| /freebsd/crypto/openssl/doc/man3/ |
| H A D | OSSL_HTTP_REQ_CTX.pod | 20 - HTTP client low-level functions
58 B<OSSL_HTTP_REQ_CTX> is a context structure for an HTTP request and response,
61 This file documents low-level HTTP functions rarely used directly. High-level
62 HTTP client functions like L<OSSL_HTTP_get(3)> and L<OSSL_HTTP_transfer(3)>
65 OSSL_HTTP_REQ_CTX_new() allocates a new HTTP request context structure,
73 which collects the HTTP request header lines.
75 OSSL_HTTP_REQ_CTX_free() frees up the HTTP request context I<rctx>.
79 OSSL_HTTP_REQ_CTX_set_request_line() adds the 1st HTTP request line to I<rctx>.
80 The HTTP method is determined by I<method_POST>,
83 an HTTP proxy shall forward the request to, otherwise they must be left NULL.
[all …]
|
| H A D | OSSL_CMP_MSG_http_perform.pod | 6 - client-side HTTP(S) transfer of a CMP request-response pair
29 where the default port is 80 for HTTP and 443 for HTTPS.
30 The HTTP path (aka "CMP alias" in this context) to use is by default C</>,
34 The function makes use of any HTTP callback function
38 It also respects any HTTP(S) proxy options set via L<OSSL_CMP_CTX_set1_proxy(3)>
40 Proxying plain HTTP is supported directly,
47 HTTP transfer for CMP is defined in RFC 6712.
|
| H A 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.
77 HTTP(S) proxy to use (unless overridden by "no_proxy" settings).
87 The HTTP client functions connect via the given proxy unless the I<server>
91 Proxying plain HTTP is supported directly,
99 may be used to modify the connection BIO used by the HTTP client,
150 seconds the overall HTTP transfer (i.e., connection setup if needed,
157 pre-established with a TLS proxy using the HTTP CONNECT method,
170 If <rctx> indicates using a proxy for HTTP (but not HTTPS), the server host
[all …]
|
| H A D | OCSP_sendreq_new.pod | 39 These functions perform an OCSP POST request / response transfer over HTTP,
40 using the HTTP request functions described in L<OSSL_HTTP_REQ_CTX(3)>.
55 and to gather the response via HTTP, using the BIO I<io> and I<path>
|
| H A D | X509_load_http.pod | 28 respectively, in ASN.1 format using HTTP from the given B<url>.
30 Maximum size of the HTTP response is 100 kB for certificates and 32 MB for CRLs
|
| /freebsd/usr.sbin/bsdconfig/share/media/ |
| H A D | httpproxy.subr | 50 # HTTP Proxy server to use. Valid examples include:
128 # Return success if able list a remote FTP directory via HTTP proxy. If
134 # The HTTP proxy server host name, IPv4 address or IPv6 address.
140 # The TCP port to connect to when communicating with the HTTP
143 # The FTP URL sent to the HTTP proxy server. Unused if
200 printf "GET %s/ HTTP/1.0\r\n\r\n" "${proxy_path%/}" |
215 /^HTTP.... 200 / {
248 # Initializes the HTTP Proxy media device. Returns success if able to confirm
249 # the existence of at least one known FTP server release path via HTTP proxy
255 # The HTTP proxy server to connect to. Usually set by having
[all …]
|
| H A D | http.subr | 67 # Prompt the user to select from a range of ``built-in'' HTTP servers or
119 # Return success if we both found and set the media type to be an HTTP server.
125 # repository on the HTTP server. Valid examples include:
141 # The HTTP host to connect to, parsed from VAR_HTTP_PATH. In the
208 # Set the name of the HTTP device to the URL
334 # Return success if able list a remote HTTP directory. If $connect_only is
339 # The HTTP server host name, IPv4 address or IPv6 address.
347 # The HTTP path sent to the server. Unused if $connect_only is
399 printf "GET %s/ HTTP/1.0\r\n\r\n" "${http_path%/}" |
414 /^HTTP.... 200 / {
[all …]
|
| /freebsd/crypto/openssl/demos/http3/ |
| H A D | README.md | 1 HTTP/3 Demo using OpenSSL QUIC and nghttp3
4 This is a simple demo of how to use HTTP/3 with OpenSSL QUIC using the HTTP/3
11 - a simple application which makes an HTTP/3 request using this adaptation
33 The demo produces the HTTP response headers in textual form as output followed
|
| /freebsd/crypto/openssl/crypto/http/ |
| H A D | http_client.c | 588 if (OSSL_TRACE_ENABLED(HTTP)) in OSSL_HTTP_REQ_CTX_nbio()
589 OSSL_TRACE(HTTP, "]\n"); /* end of error response content */ in OSSL_HTTP_REQ_CTX_nbio()
639 if (OSSL_TRACE_ENABLED(HTTP)) { in OSSL_HTTP_REQ_CTX_nbio()
641 OSSL_TRACE(HTTP, "Sending request header: [\n"); in OSSL_HTTP_REQ_CTX_nbio()
643 OSSL_TRACE_STRING(HTTP, rctx->state != OHS_WRITE_REQ || rctx->text, in OSSL_HTTP_REQ_CTX_nbio()
645 OSSL_TRACE(HTTP, "]\n"); /* end of request header or content */ in OSSL_HTTP_REQ_CTX_nbio()
658 if (OSSL_TRACE_ENABLED(HTTP)) in OSSL_HTTP_REQ_CTX_nbio()
659 OSSL_TRACE1(HTTP, "Sending request content (likely %s)\n", in OSSL_HTTP_REQ_CTX_nbio()
726 if (OSSL_TRACE_ENABLED(HTTP)) /* dump response content line */ in OSSL_HTTP_REQ_CTX_nbio()
727 OSSL_TRACE_STRING(HTTP, got_text, 1, (unsigned char *)buf, n); in OSSL_HTTP_REQ_CTX_nbio()
[all …]
|
| /freebsd/crypto/openssl/ |
| H A D | README-QUIC.md | 20 - The [demo found in `demos/http3`], which provides an HTTP/3 client example
21 using the nghttp3 HTTP/3 library.
32 communication; it is the basis for HTTP/3 [RFC 9114]; fast connection
40 ### How can I use HTTP/3 with OpenSSL?
42 There are many HTTP/3 implementations in C available. The use of one such HTTP/3
65 HTTP/3). IANA maintains a standard list of [ALPN ids] that can be used.
70 HTTP/3 so connecting to an HTTP/3 server should be possible but sending an
71 HTTP/3 request or receiving any response data is not.
|
| /freebsd/usr.sbin/bsdconfig/include/ |
| H A D | media.hlp | 19 HTTP Direct
20 Get the distribution files directly from an HTTP server.
22 If you chose to enter your own URL in the HTTP Direct menu,
|
| /freebsd/crypto/openssl/doc/man1/ |
| H A D | tsget.pod | 5 tsget - Time Stamping HTTP/HTTPS client
27 in RFC 3161, to a timestamp server over HTTP or HTTPS and storing the
33 This command sends the following HTTP request for each timestamp request:
35 POST url HTTP/1.1
54 The URL of the HTTP/HTTPS server listening for timestamp requests.
140 timestamp requests, tsa.opentsa.org listens at port 8080 for HTTP requests
144 Get a timestamp response for F<file1.tsq> over HTTP, output is written to
149 Get a timestamp response for F<file1.tsq> and F<file2.tsq> over HTTP showing
|
| /freebsd/contrib/ntp/sntp/libevent/test/ |
| H A D | regress_http.c | 4664 #define HTTP(name) HTTP_N(name, name, 0, NULL) macro
4710 HTTP(basic),
4711 HTTP(basic_trailing_space),
4712 HTTP(simple),
4713 HTTP(simple_nonconformant),
4728 HTTP(virtual_host),
4729 HTTP(post),
4730 HTTP(put),
4731 HTTP(delete),
4732 HTTP(allowed_methods),
[all …]
|
| /freebsd/contrib/libevent/test/ |
| H A D | regress_http.c | 4664 #define HTTP(name) HTTP_N(name, name, 0, NULL) macro
4710 HTTP(basic),
4711 HTTP(basic_trailing_space),
4712 HTTP(simple),
4713 HTTP(simple_nonconformant),
4728 HTTP(virtual_host),
4729 HTTP(post),
4730 HTTP(put),
4731 HTTP(delete),
4732 HTTP(allowed_methods),
[all …]
|
| /freebsd/crypto/openssl/test/ |
| H A D | trace_api_test.c | 62 SET_EXPECTED_CAT_NAME(HTTP); in test_trace_categories()
105 OSSL_TRACE_BEGIN(HTTP) { in put_trace_output()
115 } OSSL_TRACE_END(HTTP); in put_trace_output()
|
| /freebsd/contrib/ntp/sntp/libevent/ |
| H A D | ChangeLog-1.4 | 17 o Do not send an HTTP error when we've already closed or responded. (4fd2dd9 Pavel Plesov)
26 o Do not abort HTTP requests missing a reason string. (29d7b32 Pierre Phaneuf)
54 o Remove the limit on size of HTTP headers by removing static buffers.
91 o Support multi-line HTTP headers; based on a patch from Moshe Litvin
107 o Fix connection keep-alive behavior for HTTP/1.0
135 o include Content-Length in reply for HTTP/1.0 requests with keep-alive
148 …o Send CRLF after each chunk in HTTP output, for compliance with RFC2626. Patch from "propanbutan…
149 …4_t parsing function, with unit tests, so we can apply Scott Lamb's fix to allow large HTTP values.
150 o Use a 64-bit field to hold HTTP content-lengths. Patch from Scott Lamb.
168 o always generate Date and Content-Length headers for HTTP/1.1 replies
[all …]
|
| /freebsd/contrib/libevent/ |
| H A D | ChangeLog-1.4 | 17 o Do not send an HTTP error when we've already closed or responded. (4fd2dd9 Pavel Plesov)
26 o Do not abort HTTP requests missing a reason string. (29d7b32 Pierre Phaneuf)
54 o Remove the limit on size of HTTP headers by removing static buffers.
91 o Support multi-line HTTP headers; based on a patch from Moshe Litvin
107 o Fix connection keep-alive behavior for HTTP/1.0
135 o include Content-Length in reply for HTTP/1.0 requests with keep-alive
148 …o Send CRLF after each chunk in HTTP output, for compliance with RFC2626. Patch from "propanbutan…
149 …4_t parsing function, with unit tests, so we can apply Scott Lamb's fix to allow large HTTP values.
150 o Use a 64-bit field to hold HTTP content-lengths. Patch from Scott Lamb.
168 o always generate Date and Content-Length headers for HTTP/1.1 replies
[all …]
|
| /freebsd/contrib/ntp/scripts/update-leap/ |
| H A D | update-leap.in | 30 use HTTP::Tiny 0.056;
46 # HTTP - No TLS/SSL - (not recommended)
277 # HTTP::Tiny doesn't export a method to explicitly close a connected
287 $http = HTTP::Tiny->new(%SSL_ATTRS);
292 $http = HTTP::Tiny->new();
467 HTTP::Tiny - version >= 0.056
|
| /freebsd/contrib/bearssl/samples/ |
| H A D | README.txt | 6 handshake, sends a basic HTTP GET request, and dumps the complete
16 single HTTP request (that it does not really parse; it just waits for
|
| /freebsd/contrib/ntp/sntp/libevent/sample/ |
| H A D | https-client.c | 238 enum { HTTP, HTTPS } type = HTTP; in main() enumerator
520 if (type == HTTP && ssl) in main()
|
| /freebsd/contrib/libevent/sample/ |
| H A D | https-client.c | 238 enum { HTTP, HTTPS } type = HTTP; in main() enumerator
520 if (type == HTTP && ssl) in main()
|
| /freebsd/crypto/openssl/doc/man7/ |
| H A D | ossl-guide-quic-multi-stream.pod | 162 some HTTP/1.0 requests to it, and read back the responses. Note that HTTP/1.0
198 two different HTTP requests to the server. For the purposes of demonstration the
216 this example we will be sending a different HTTP request on each stream. To
217 avoid repeating too much code we write a simple helper function to send an HTTP
237 appropriate HTTP requests. We can then call our helper function above to send
246 /* Write an HTTP GET request on each of our streams to the peer */
248 printf("Failed to write HTTP request on stream 1\n");
253 printf("Failed to write HTTP request on stream 2\n");
352 * In our hypothetical HTTP/1.0 over QUIC protocol that we are using we
376 we don't do that in this example because we assume that the HTTP application
|
| /freebsd/crypto/openssl/demos/quic/ |
| H A D | README.md | 8 - [HTTP/3 Client Demo](../http3/)
|
| /freebsd/crypto/openssl/test/recipes/95-test_external_cf_quiche_data/ |
| H A D | quiche-server.sh | 27 --http-version HTTP/0.9 --root "$SRCTOP" --no-grease --disable-hystart &
|
| /freebsd/release/packages/ucl/ |
| H A D | fetch-all.ucl | 5 HTTP or FTP.
|