Searched full:http (Results 1 – 25 of 548) sorted by relevance
12345678910>>...22
/Zephyr-latest/subsys/net/lib/http/ |
D | Kconfig | 5 bool "HTTP Parser support" 13 bool "HTTP Parser for URL support" 20 bool "HTTP strict parsing" 26 bool "HTTP client API" 30 HTTP client API 33 bool "HTTP Server [EXPERIMENTAL]" 44 int "HTTP server thread stack size" 47 HTTP server thread stack size for processing RX/TX events. 50 int "Number of HTTP Server Instances" 54 This setting determines the number of http services that the server supports. [all …]
|
D | README_http_parser | 1 HTTP Parser Support in Zephyr 4 The http-parser library* from the nodejs project is a downstream of an 8 https://github.com/nodejs/http-parser/releases/tag/v2.7.1 9 https://github.com/nodejs/http-parser/archive/v2.7.1.tar.gz 14 * "http-parser" is the project's name, "http_parser" is used in filenames.
|
/Zephyr-latest/samples/net/sockets/http_client/ |
D | README.rst | 1 .. zephyr:code-sample:: sockets-http-client 2 :name: HTTP Client 5 Implement an HTTP(S) client that issues a variety of HTTP requests. 10 This sample application implements an HTTP(S) client that will do an HTTP 11 or HTTPS request and wait for the response from the HTTP server. 27 Build the http-client sample application like this: 54 The default certificates used by Socket HTTP Client and ``https-server.py`` 59 Running http-server in Linux Host 62 You can run this ``http-client`` sample application in QEMU 63 and run the ``http-server.py`` (from net-tools) on a Linux host. [all …]
|
D | Kconfig | 1 # Private config options for http-client sample app 6 mainmenu "Networking http-client sample application" 9 int "Send a sample HTTP query this many times" 12 Send a sample HTTP query this many times before exiting. A value of
|
D | prj.conf | 33 # Address of HTTP IPv4 server 36 # Address of HTTP IPv6 server 39 # HTTP
|
/Zephyr-latest/samples/net/sockets/dumb_http_server_mt/ |
D | README.rst | 1 .. zephyr:code-sample:: socket-dumb-http-server-mt 2 :name: Dumb HTTP server (multi-threaded) 5 Implement a simple HTTP server supporting simultaneous connections using BSD sockets. 11 skeleton HTTP server using a BSD Sockets compatible API. 12 This sample has similar functionality as :zephyr:code-sample:`socket-dumb-http-server` 15 This HTTP server example is very minimal and does not really parse an incoming 16 HTTP request, just reads and discards it, and always serves a single static 42 browser: http://192.0.2.1:8080/ or http://[2001:db8::1]:8080/ 50 $ curl http://192.0.2.1:8080/ 52 Finally, you can run an HTTP profiling/load tool like Apache Bench [all …]
|
/Zephyr-latest/include/zephyr/net/http/ |
D | client.h | 2 * @brief HTTP client API 4 * An API for applications do HTTP requests 17 * @brief HTTP client API 18 * @defgroup http_client HTTP client API 27 #include <zephyr/net/http/parser.h> 59 * @param req HTTP request information 74 * HTTP headers when the HTTP request is sent. Usage of this is optional. 77 * @param req HTTP request information 93 * @param rsp HTTP response information 103 * HTTP response from the server. [all …]
|
D | server.h | 14 * @brief HTTP server API 16 * @defgroup http_server HTTP server API 26 #include <zephyr/net/http/parser.h> 27 #include <zephyr/net/http/hpack.h> 28 #include <zephyr/net/http/status.h> 60 #define HTTP2_PREFACE "PRI * HTTP/2.0\r\n\r\nSM\r\n\r\n" 65 * @brief HTTP server resource type. 89 /** Bitmask of supported HTTP methods (@ref http_method). */ 180 /** @brief HTTP header representation */ 186 /** @brief HTTP request context */ [all …]
|
D | status.h | 2 * @brief HTTP response status codes 15 * @brief HTTP response status codes 16 * @defgroup http_status_codes HTTP response status codes 28 * @brief HTTP response status codes 30 * @note HTTP response status codes are subject to IANA approval. 32 …* @see <a href="https://www.iana.org/assignments/http-status-codes">Hypertext Transfer Protocol (H… 34 …* @see <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Status">HTTP response status cod… 94 HTTP_505_HTTP_VERSION_NOT_SUPPORTED = 505, /**< HTTP Version Not Supported */
|
/Zephyr-latest/samples/net/sockets/dumb_http_server/ |
D | README.rst | 1 .. zephyr:code-sample:: socket-dumb-http-server 2 :name: Dumb HTTP server 5 Implement a simple, portable, HTTP server using BSD sockets. 11 skeleton HTTP server using a BSD Sockets compatible API. The purpose of 13 portable to both POSIX and Zephyr. As such, this HTTP server example is 14 kept very minimal and does not really parse an incoming HTTP request, 18 perform performance/regression testing using existing HTTP diagnostic 43 browser: http://192.0.2.1:8080/ . You should see a page with a sample 50 $ curl http://192.0.2.1:8080/ 52 Finally, you can run an HTTP profiling/load tool like Apache Bench [all …]
|
/Zephyr-latest/samples/net/sockets/http_server/ |
D | README.rst | 1 .. zephyr:code-sample:: sockets-http-server 2 :name: HTTP Server 5 Implement an HTTP(s) Server demonstrating various resource types. 12 The server supports the HTTP/1.1 protocol which can also be upgraded to HTTP/2, 13 it also support native HTTP/2 protocol without upgrading. 43 When the server is up, we can make requests to the server using either HTTP/1.1 or 44 HTTP/2 protocol from the host machine. 46 **With HTTP/1.1:** 48 - Using a browser: ``http://192.0.2.1/`` 49 - Using curl: ``curl -v --compressed http://192.0.2.1/`` [all …]
|
D | Kconfig | 9 bool "Enable http service" 13 int "Port number for http service" 33 Web browsers only use HTTP/2 over HTTPS, and use ALPN to determine if a 34 server supports HTTP/2. If this option is enabled, web browsers can use 35 HTTP/2 to communicate with the server. However web browsers are stricter 36 with security when using HTTP/2, at a minimum you will need to add the CA
|
D | sample.yaml | 2 description: HTTP Server Sample 9 - http 18 sample.net.sockets.http.server: {}
|
/Zephyr-latest/doc/connectivity/networking/api/ |
D | http_client.rst | 3 HTTP Client 13 The HTTP client library allows you to send HTTP requests and 14 parse HTTP responses. The library communicates over the sockets 20 either a plain TCP socket (HTTP) or a TLS socket (HTTPS). 25 The API of the HTTP client library has a single function. 37 req.protocol = "HTTP/1.1"; 43 * to the HTTP server. 72 See :zephyr:code-sample:`HTTP client sample application <sockets-http-client>` for
|
D | http_server.rst | 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. [all …]
|
/Zephyr-latest/doc/services/portability/posix/overview/ |
D | posix.svg | 1 <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> 2 …http://www.w3.org/2000/svg" style="background-color: rgb(255, 255, 255);" xmlns:xlink="http://www.…
|
/Zephyr-latest/doc/kernel/services/threads/ |
D | thread_states.svg | 2 <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> 3 …http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.1" width="601px"…
|
/Zephyr-latest/subsys/net/lib/shell/ |
D | http.c | 11 #include <zephyr/net/http/service.h> 12 #include <zephyr/net/http/server.h> 13 #include <zephyr/net/http/method.h> 14 #include <zephyr/net/http/parser.h> 80 PR("No HTTP services and resources found.\n"); in cmd_net_http() 93 "HTTP information"); in cmd_net_http() 99 SHELL_SUBCMD_ADD((net), http, NULL, 100 "Show HTTP services.",
|
/Zephyr-latest/doc/kernel/services/scheduling/ |
D | timeslicing.svg | 1 <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> 2 …http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.1" width="750px"…
|
D | cooperative.svg | 1 <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> 2 …http://www.w3.org/2000/svg" style="background-color: rgb(255, 255, 255);" xmlns:xlink="http://www.…
|
D | preemptive.svg | 1 <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> 2 …http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.1" width="750px"…
|
/Zephyr-latest/samples/net/prometheus/ |
D | README.rst | 13 via an HTTP endpoint on your application's instance, enabling Prometheus to 33 When the server is up, we can make requests to the server using HTTP/1.1. 35 **With HTTP/1.1:** 37 - Using a browser: ``http://192.0.2.1/metrics`` 50 - ``CONFIG_HTTP_SERVER_MAX_CLIENTS``: Defines the maximum number of HTTP/2 53 - ``CONFIG_HTTP_SERVER_MAX_STREAMS``: Specifies the maximum number of HTTP/2 57 for each client. This limits the maximum length of an individual HTTP header 60 - ``CONFIG_HTTP_SERVER_MAX_URL_LENGTH``: Specifies the maximum length of an HTTP
|
/Zephyr-latest/doc/kernel/drivers/ |
D | device_driver_model.svg | 2 <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> 3 …http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.1" width="781px"…
|
/Zephyr-latest/doc/build/dts/ |
D | zephyr_dt_i2c_high_level.svg | 2 <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> 3 …http://www.w3.org/2000/svg" style="background-color: rgb(255, 255, 255);" xmlns:xlink="http://www.…
|
/Zephyr-latest/samples/net/sockets/websocket_client/ |
D | prj.conf | 22 # Address of HTTP IPv4 server 25 # Address of HTTP IPv6 server 28 # HTTP & Websocket
|
12345678910>>...22