Lines Matching refs:HTTP

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).
85 The HTTP client functions connect via the given proxy unless the I<server>
89 Proxying plain HTTP is supported directly,
97 may be used to modify the connection BIO used by the HTTP client,
146 seconds the overall HTTP transfer (i.e., connection setup if needed,
153 pre-established with a TLS proxy using the HTTP CONNECT method,
166 If <rctx> indicates using a proxy for HTTP (but not HTTPS), the server host
172 If I<req> is NULL the HTTP GET method will be used to send the request
173 else HTTP POST with the contents of I<req> and optional I<content_type>, where
176 The optional list I<headers> may contain additional custom HTTP header lines.
179 is included in the HTTP header of the response and return an error if not.
185 the subsequent HTTP transfer (sending the request and receiving a response)
189 when opening the HTTP transfer will be used instead.
191 after receiving a response, which is the default behavior for HTTP 1.0.
196 OSSL_HTTP_exchange() exchanges any form of HTTP request and response
200 If the HTTP method is GET and I<redirection_url>
202 the server may return with HTTP code 301 (MOVED_PERMANENTLY) or 302 (FOUND).
215 OSSL_HTTP_get() uses HTTP GET to obtain data from I<bio> if non-NULL,
217 It supports redirection via HTTP status code 301 or 302.  It is meant for
229 OSSL_HTTP_transfer() exchanges an HTTP request and response
244 It must be 1 if no error occurred during the HTTP transfer and 0 otherwise.
251 other HTTP client implementations such as wget, curl, and git.