Lines Matching full:http
3 HTTP Server
13 Zephyr provides an HTTP server library, which allows to register HTTP services
14 and HTTP resources associated with those services. The server creates a listening
16 It's possible to communicate over a plain TCP socket (HTTP) or a TLS socket (HTTPS).
17 Both, HTTP/1.1 (RFC 2616) and HTTP/2 (RFC 9113) protocol versions are supported.
38 Zephyr provides a sample demonstrating HTTP(s) server operation and various
39 resource types usage. See :zephyr:code-sample:`sockets-http-server` for more
45 A few prerequisites are needed in order to enable HTTP server functionality in
48 First of all, the HTTP server has to be enabled in applications configuration file
56 All HTTP services and HTTP resources are placed in a dedicated linker section.
85 You need to define a separate linker section for each HTTP service
94 The application needs to define an HTTP service (or multiple services), with
100 #include <zephyr/net/http/service.h>
111 #include <zephyr/net/http/service.h>
130 Once HTTP(s) service is defined, resources can be registered for it with
135 option is set, then it is possible to match several incoming HTTP requests
211 content-encoding to the HTTP header.
308 the HTTP server:
310 * The ``status`` field allows the application to send an HTTP response code. If
314 send any arbitrary HTTP headers. If not populated, only Transfer-Encoding and
354 /* We need HTTP/1.1 Get method for upgrading */
368 of scope of this guide. See :zephyr:code-sample:`sockets-http-server` for an
374 The application can register an interest in any specific HTTP request headers.