Searched refs:HTTP (Results 1 – 25 of 588) sorted by relevance
12345678910>>...24
| /third_party/python/Doc/library/ |
| D | http.rst | 1 :mod:`http` --- HTTP modules
5 :synopsis: HTTP status codes and messages
10 pair: HTTP; protocol
11 single: HTTP; http (standard module)
18 * :mod:`http.client` is a low-level HTTP protocol client; for high-level URL
20 * :mod:`http.server` contains basic HTTP server classes based on :mod:`socketserver`
24 :mod:`http` is also a module that defines a number of HTTP status codes and
31 A subclass of :class:`enum.IntEnum` that defines a set of HTTP status codes,
52 HTTP status codes
62 ``100`` ``CONTINUE`` HTTP/1.1 :rfc:`7231`, Section 6.2.1
[all …]
|
| D | http.client.rst | 1 :mod:`http.client` --- HTTP protocol client
5 :synopsis: HTTP and HTTPS protocol client (requires sockets).
10 pair: HTTP; protocol
11 single: HTTP; http.client (standard module)
17 This module defines classes which implement the client side of the HTTP and
19 :mod:`urllib.request` uses it to handle URLs that use HTTP and HTTPS.
24 is recommended for a higher-level HTTP client interface.
37 An :class:`HTTPConnection` instance represents one transaction with an HTTP
40 string if it has the form ``host:port``, else the default HTTP port (80) is
45 to use as the source address the HTTP connection is made from.
[all …]
|
| D | http.server.rst | 1 :mod:`http.server` --- HTTP servers
5 :synopsis: HTTP server and request handlers.
11 pair: HTTP; protocol
17 This module defines classes for implementing HTTP servers.
26 It creates and listens at the HTTP socket, dispatching the requests to a
58 This class is used to handle the HTTP requests that arrive at the server. By
59 itself, it cannot respond to any actual HTTP requests; it must be subclassed
90 Contains the string representation of the HTTP request line. The
107 Contains the version string from the request. For example, ``'HTTP/1.0'``.
112 variable. This instance parses and manages the headers in the HTTP
[all …]
|
| D | http.cookies.rst | 1 :mod:`http.cookies` --- HTTP state management
5 :synopsis: Support for HTTP state management (cookies).
15 cookies, an HTTP state management mechanism. It supports both simple string-only
60 the value to a string. Values received from HTTP are kept as strings.
65 HTTP cookie handling for web *clients*. The :mod:`http.cookiejar` and
68 :rfc:`2109` - HTTP State Management Mechanism
98 Return a string representation suitable to be sent as HTTP headers. *attrs* and
107 supports JavaScript, will act the same as if the HTTP headers was sent.
145 in HTTP requests, and is not accessible through JavaScript. This is intended
194 Return a string representation of the Morsel, suitable to be sent as an HTTP
[all …]
|
| /third_party/nghttp2/doc/sources/ |
| D | nghttpx-howto.rst | 3 nghttpx - HTTP/2 proxy - HOW-TO
6 :doc:`nghttpx.1` is a proxy translating protocols between HTTP/2 and
7 other protocols (e.g., HTTP/1). It operates in several modes and each
17 HTTP/3, HTTP/2 and HTTP/1 clients to backend servers. This is also
18 known as "HTTP/2 router".
26 in :option:`--frontend` option. HTTP/2 and HTTP/1 are available on
27 the frontend, and an HTTP/1 connection can be upgraded to HTTP/2 using
28 HTTP Upgrade. Starting HTTP/2 connection by sending HTTP/2 connection
31 In order to receive HTTP/3 traffic, use ``quic`` parameter in
43 both HTTP/2 and HTTP/1 in backend connections at the same time. Note
[all …]
|
| D | h2load-howto.rst | 3 h2load - HTTP/2 benchmarking tool - HOW-TO
6 :doc:`h2load.1` is benchmarking tool for HTTP/2 and HTTP/1.1. It
35 cleartext connection, the default protocol is HTTP/2. To change the
37 For convenience, :option:`--h1` option forces HTTP/1.1 for both
87 HTTP/2 has flow control and it may affect benchmarking results. By
113 By default, if \http:// URI is given, HTTP/2 protocol is used. To
135 HTTP/3
138 h2load supports HTTP/3 if it is built with HTTP/3 enabled. HTTP/3
141 In order to send HTTP/3 request, specify ``h3`` to
|
| /third_party/nghttp2/ |
| D | README.rst | 1 nghttp2 - HTTP/2 C Library
7 The framing layer of HTTP/2 is implemented as a reusable C library.
8 On top of that, we have implemented an HTTP/2 client, server and
10 HTTP/2.
18 <https://tools.ietf.org/html/rfc7540>`_ HTTP/2 and `RFC 7541
20 HTTP/2. Now we are updating our code to implement `RFC 9113
32 * https://nghttp2.org/ (TLS + ALPN/NPN and HTTP/3)
35 ``http/1.1`` via ALPN/NPN and requires TLSv1.2 for HTTP/2
38 It also supports HTTP/3.
40 * http://nghttp2.org/ (HTTP Upgrade and HTTP/2 Direct)
[all …]
|
| /third_party/openssl/doc/man3/ |
| D | OSSL_HTTP_REQ_CTX.pod | 19 - HTTP client low-level functions
55 B<OSSL_HTTP_REQ_CTX> is a context structure for an HTTP request and response,
58 This file documents low-level HTTP functions rarely used directly. High-level
59 HTTP client functions like L<OSSL_HTTP_get(3)> and L<OSSL_HTTP_transfer(3)>
62 OSSL_HTTP_REQ_CTX_new() allocates a new HTTP request context structure,
70 which collects the HTTP request header lines.
72 OSSL_HTTP_REQ_CTX_free() frees up the HTTP request context I<rctx>.
75 OSSL_HTTP_REQ_CTX_set_request_line() adds the HTTP request line to the context.
76 The HTTP method is determined by I<method_POST>,
80 I<path> is the HTTP request path; if left NULL, C</> is used.
[all …]
|
| D | OSSL_CMP_MSG_http_perform.pod | 6 - client-side HTTP(S) transfer of a CMP request-response pair
21 The default port is 80 for HTTP and 443 for HTTPS; the default path is "/".
24 The function makes use of any HTTP callback function
28 It also respects any HTTP(S) proxy options set via L<OSSL_CMP_CTX_set1_proxy(3)>
30 Proxying plain HTTP is supported directly,
37 HTTP transfer for CMP is defined in RFC 6712.
|
| D | OSSL_HTTP_transfer.pod | 13 - HTTP client high-level functions
55 OSSL_HTTP_open() initiates an HTTP session using the I<bio> argument if not
62 defaulting to 80 for HTTP or 443 for HTTPS.
75 HTTP(S) proxy to use (unless overridden by "no_proxy" settings).
84 The HTTP client functions connect via the given proxy unless the I<server>
87 Proxying plain HTTP is supported directly,
95 may be used to modify the connection BIO used by the HTTP client,
144 seconds the overall HTTP transfer (i.e., connection setup if needed,
151 pre-established with a TLS proxy using the HTTP CONNECT method,
164 If <rctx> indicates using a proxy for HTTP (but not HTTPS), the server hostname
[all …]
|
| /third_party/ejdb/src/jbs/ |
| D | README.md | 1 # REST/Websocket HTTP server.
14 -p, --port=NUM HTTP server port numer. Default: 9191
16 -k, --key=<> PEM private key file for TLS 1.2 HTTP server.
17 -c, --certs=<> PEM certificates file for TLS 1.2 HTTP server.
18 -a, --access=TOKEN|@FILE Access token to match 'X-Access-Token' HTTP header value.
20 -C, --cors Enable COSR response headers for HTTP server
|
| /third_party/node/deps/npm/node_modules/agent-base/ |
| D | README.md | 8 given callback function when sending outbound HTTP requests.
15 …* [`http-proxy-agent`][http-proxy-agent]: An HTTP(s) proxy `http.Agent` implementation for HTTP en…
16 …* [`https-proxy-agent`][https-proxy-agent]: An HTTP(s) proxy `http.Agent` implementation for HTTPS…
17 …* [`pac-proxy-agent`][pac-proxy-agent]: A PAC file proxy `http.Agent` implementation for HTTP and …
18 …roxy-agent`][socks-proxy-agent]: A SOCKS (v4a) proxy `http.Agent` implementation for HTTP and HTTPS
35 for every HTTP request (i.e. the equivalent of `agent: false` option):
76 for that HTTP request to that agent:
91 for every HTTP request that it is used as the `agent` for. The callback function
93 used as the underlying socket in the HTTP request.
108 the callback function `cb` once created, and the HTTP request will
[all …]
|
| /third_party/node/deps/npm/node_modules/socks-proxy-agent/node_modules/agent-base/ |
| D | README.md | 8 given callback function when sending outbound HTTP requests.
15 …* [`http-proxy-agent`][http-proxy-agent]: An HTTP(s) proxy `http.Agent` implementation for HTTP en…
16 …* [`https-proxy-agent`][https-proxy-agent]: An HTTP(s) proxy `http.Agent` implementation for HTTPS…
17 …* [`pac-proxy-agent`][pac-proxy-agent]: A PAC file proxy `http.Agent` implementation for HTTP and …
18 …roxy-agent`][socks-proxy-agent]: A SOCKS (v4a) proxy `http.Agent` implementation for HTTP and HTTPS
35 for every HTTP request (i.e. the equivalent of `agent: false` option):
76 for that HTTP request to that agent:
91 for every HTTP request that it is used as the `agent` for. The callback function
93 used as the underlying socket in the HTTP request.
108 the callback function `cb` once created, and the HTTP request will
[all …]
|
| /third_party/ejdb/src/jbr/ |
| D | README.md | 1 # HTTP REST/Websocket API endpoint
3 EJDB engine provides the ability to start a separate HTTP/Websocket endpoint worker exposing networ…
17 -p, --port=NUM HTTP server port numer. Default: 9191
19 -k, --key=<> PEM private key file for TLS 1.2 HTTP server.
20 -c, --certs=<> PEM certificates file for TLS 1.2 HTTP server.
21 -a, --access=TOKEN|@FILE Access token to match 'X-Access-Token' HTTP header value.
23 -C, --cors Enable COSR response headers for HTTP server
37 ## HTTP API
39 HTTP endpoint may be protected by a token specified with `--access` flag or C API `EJDB_HTTP` struc…
40 If access token was set, client should provide `X-Access-Token` HTTP header.
[all …]
|
| /third_party/skia/third_party/externals/brotli/fetch-spec/ |
| D | shared-brotli-fetch-spec.txt | 12 This document specifies how the client and server negotiate the dictionary over HTTP.
13 A high level overview is as follows: The server adds an HTTP header to the response
15 then caches it so it can be reused. The server also adds a checksum to an HTTP header
24 Additions to `4.5. HTTP-network-or-cache fetch`
26 Add to point `15. Modify httpRequest’s header list per HTTP.`:
33 Additions to `4.6. HTTP-network fetch`
72 explained in HTTP. [HTTP] [HTTP-SEMANTICS] [HTTP-COND] [HTTP-CACHING]
73 [HTTP-AUTH]
84 [HTTP-network-or-cache](https://fetch.spec.whatwg.org/#concept-http-network-or-cache-fetch)
|
| /third_party/curl/ |
| D | backport-0004-CVE-2023-23914-CVE-2023-23915.patch | 37 +HTTP
38 +HTTP proxy
48 +HTTP/1.1 200 OK
52 +HTTP/1.1 200 OK
59 +HTTP/1.1 200 OK
94 +GET http://this.hsts.example./%TESTNUMBER HTTP/1.1
100 +GET http://another.example.com/%TESTNUMBER0002 HTTP/1.1
|
| /third_party/node/doc/api/ |
| D | http2.md | 1 # HTTP/2
10 description: HTTP/2 is now Stable. Previously, it had been Experimental.
18 The `http2` module provides an implementation of the [HTTP/2][] protocol. It
28 support for HTTP/2 protocol features. It is specifically *not* designed for
29 compatibility with the existing [HTTP/1][] module API. However,
38 The following illustrates a simple HTTP/2 server using the Core API.
40 [unencrypted HTTP/2][HTTP/2 Unencrypted], the use of
75 The following illustrates an HTTP/2 client:
111 session between an HTTP/2 client and server. Instances of this class are *not*
124 new HTTP/2 connection is received. Client-side `Http2Session` instances are
[all …]
|
| /third_party/node/deps/npm/node_modules/https-proxy-agent/ |
| D | README.md | 3 ### An HTTP(s) proxy `http.Agent` implementation for HTTPS
7 HTTP or HTTPS proxy server, and can be used with the built-in `https` module.
10 server and issues the [CONNECT HTTP method][CONNECT], which tells the proxy to
13 Since this agent implements the CONNECT HTTP method, it also works with other
38 // HTTP/HTTPS proxy to connect to
64 // HTTP/HTTPS proxy to connect to
98 to the specified "HTTP(s) proxy server" in order to proxy HTTPS and/or WebSocket
99 requests. This is achieved by using the [HTTP `CONNECT` method][CONNECT].
107 * `headers` - Object - Additional HTTP headers to be sent on the HTTP CONNECT method.
|
| /third_party/node/deps/npm/node_modules/http-proxy-agent/ |
| D | README.md | 3 ### An HTTP(s) proxy `http.Agent` implementation for HTTP
7 HTTP or HTTPS proxy server, and can be used with the built-in `http` module.
9 __Note:__ For HTTP proxy usage with the `https` module, check out
30 // HTTP/HTTPS proxy to connect to
34 // HTTP endpoint for the proxy to connect to
|
| /third_party/node/deps/npm/node_modules/http-signature/ |
| D | http_signing.md | 4 and replay resistance to HTTP REST requests. It is intended to be used over
16 This protocol is intended to provide a standard way for clients to sign HTTP
17 requests. RFC2617 (HTTP Authentication) defines Basic and Digest authentication
30 HTTP requests, but to date, none have been placed in the public domain as a
42 HTTP `Date` header.
79 OPTIONAL. The `headers` parameter is used to specify the list of HTTP headers
80 used to sign the request. If specified, it should be a quoted list of HTTP
82 HTTP header is signed, which is the `Date` header. Note that the list MUST be
84 include the HTTP request line in the signature calculation, use the special
86 HTTP linguism, the request-line is defined in RFC 2616, and as the outlier from
[all …]
|
| /third_party/nghttp2/doc/ |
| D | programmers-guide.rst | 8 perform any I/O. nghttp2 only performs HTTP/2 protocol stuff based on
23 case. This is because you probably want to support HTTP/1 which
25 own HTTP/1 stack or use existing third-party library, and bind them
66 There is a question when we are safe to close HTTP/2 session without
108 HTTP Messaging
111 By default, nghttp2 library checks HTTP messaging rules described in
112 `HTTP/2 specification, section 8
121 client and server model of HTTP. That is, even if the validation is
124 For HTTP request, including those carried by PUSH_PROMISE, HTTP
135 For HTTP response, HTTP message starts with zero or more HEADERS
[all …]
|
| D | nghttpx.1.rst | 17 A reverse proxy for HTTP/3, HTTP/2, and HTTP/1.
140 refers to HTTP/2 over TLS. But in this option, it may
141 mean HTTP/2 over cleartext TCP unless "tls" keyword is
231 parameter, HTTP/2 :scheme pseudo header field is changed
278 contacted). It is expected that the HTTP response is
323 are replied with 200 HTTP status, without no body.
329 To receive HTTP/3 (QUIC) traffic, specify "quic"
359 proxy is used when the backend connection is HTTP/2.
458 (and/or streams in case of HTTP/2) per origin host.
462 HTTP/2). To limit the number of connections per
[all …]
|
| /third_party/node/deps/npm/node_modules/socks/docs/examples/javascript/ |
| D | connectExample.md | 9 …HTTP request to receive a response. It's worth noting that there are many socks-http-agents that c…
42 info.socket.write('GET /json HTTP/1.1\nHost: ip-api.com\n\n');
46 HTTP/1.1 200 OK
102 info.socket.write('GET /json HTTP/1.1\nHost: ip-api.com\n\n');
106 HTTP/1.1 200 OK
166 info.socket.write('GET /json HTTP/1.1\nHost: ip-api.com\n\n');
170 HTTP/1.1 200 OK
225 info.socket.write('GET /json HTTP/1.1\nHost: ip-api.com\n\n');
229 HTTP/1.1 200 OK
|
| /third_party/node/deps/npm/node_modules/socks/docs/examples/typescript/ |
| D | connectExample.md | 9 …HTTP request to receive a response. It's worth noting that there are many socks-http-agents that c…
42 info.socket.write('GET /json HTTP/1.1\nHost: ip-api.com\n\n');
46 HTTP/1.1 200 OK
103 info.socket.write('GET /json HTTP/1.1\nHost: ip-api.com\n\n');
107 HTTP/1.1 200 OK
168 info.socket.write('GET /json HTTP/1.1\nHost: ip-api.com\n\n');
172 HTTP/1.1 200 OK
228 info.socket.write('GET /json HTTP/1.1\nHost: ip-api.com\n\n');
232 HTTP/1.1 200 OK
|
| /third_party/libwebsockets/READMEs/ |
| D | mainpage.md | 5 - HTTP(S) serving and client operation
6 - HTTP/2 support for serving and client operation
8 - HTTP(S) apis for file transfer and upload
9 - HTTP 1 + 2 POST form handling (including multipart / file upload)
|
12345678910>>...24