mirror of
https://github.com/curl/curl.git
synced 2026-08-25 07:13:32 +03:00
earlier -> lower/older
This commit is contained in:
parent
ebeeec8d6d
commit
3f6073553f
12 changed files with 14 additions and 15 deletions
|
|
@ -49,7 +49,7 @@ placeholders for the version you build.
|
|||
|
||||
## Build with OpenSSL or fork
|
||||
|
||||
OpenSSL v3.5.0+ requires *ngtcp2* v1.12.0+. Earlier versions do not work.
|
||||
OpenSSL v3.5.0+ requires *ngtcp2* v1.12.0+. Lower versions do not work.
|
||||
|
||||
Build OpenSSL (v3.5.0+) or fork AWS-LC, BoringSSL, LibreSSL or quictls:
|
||||
|
||||
|
|
@ -256,7 +256,7 @@ See this [list of public HTTP/3 servers](https://bagder.github.io/HTTP3-test/)
|
|||
|
||||
### HTTPS eyeballing
|
||||
|
||||
With option `--http3` curl attempts earlier HTTP versions as well should the
|
||||
With option `--http3` curl attempts lower HTTP versions as well should the
|
||||
connect attempt via HTTP/3 fail "fast enough". This strategy is similar
|
||||
to IPv4/6 happy eyeballing where the alternate address family is used in
|
||||
parallel after a short delay.
|
||||
|
|
|
|||
|
|
@ -429,7 +429,7 @@ for dynamic import symbols.
|
|||
Schannel (from Windows SSPI), is the native SSL library in Windows. Schannel
|
||||
in Windows <= XP is unable to connect to servers that no longer support the
|
||||
legacy handshakes and algorithms used by those versions. If you are using curl
|
||||
in one of those earlier versions of Windows you should choose another SSL
|
||||
in one of those older versions of Windows you should choose another SSL
|
||||
backend such as OpenSSL.
|
||||
|
||||
# Android
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ Example:
|
|||
# `--http3-only`
|
||||
|
||||
Instruct curl to use HTTP/3 to the host in the URL, with no fallback to
|
||||
earlier HTTP versions. HTTP/3 can only be used for HTTPS and not for HTTP
|
||||
lower HTTP versions. HTTP/3 can only be used for HTTPS and not for HTTP
|
||||
URLs. For HTTP, this option triggers an error.
|
||||
|
||||
This option allows a user to avoid using the Alt-Svc method of upgrading to
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ Example:
|
|||
|
||||
# `--http3`
|
||||
|
||||
Attempt HTTP/3 to the host in the URL, but fallback to earlier HTTP versions
|
||||
Attempt HTTP/3 to the host in the URL, but fallback to lower HTTP versions
|
||||
if the HTTP/3 connection establishment fails or is slow. HTTP/3 is only
|
||||
available for HTTPS and not for HTTP URLs.
|
||||
|
||||
|
|
|
|||
|
|
@ -41,7 +41,7 @@ int main(void)
|
|||
if(curl) {
|
||||
curl_easy_setopt(curl, CURLOPT_URL, "https://example.com");
|
||||
|
||||
/* Use HTTP/3 but fallback to earlier HTTP if necessary */
|
||||
/* Use HTTP/3 but fallback to lower HTTP if necessary */
|
||||
curl_easy_setopt(curl, CURLOPT_HTTP_VERSION, CURL_HTTP_VERSION_3);
|
||||
|
||||
/* Perform the request, result gets the return code */
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ of data and even latency. In the case of QUIC, resumption may send
|
|||
application data without having seen any reply from the server, hence
|
||||
this is named 0-RTT data.
|
||||
|
||||
The exact mechanism of session tickets in TLSv1.2 (and earlier) and
|
||||
The exact mechanism of session tickets in TLSv1.2 (and lower) and
|
||||
TLSv1.3 differs. TLSv1.2 tickets have several weaknesses (that can
|
||||
be exploited by attackers) which TLSv1.3 then fixed. See
|
||||
[Session Tickets in the real world](https://words.filippo.io/we-need-to-talk-about-session-tickets/)
|
||||
|
|
|
|||
|
|
@ -80,7 +80,7 @@ that both HTTP/1.1 and HTTP/2 were offered.
|
|||
## CURL_HTTP_VERSION_3
|
||||
|
||||
(Added in 7.66.0) This option makes libcurl attempt to use HTTP/3 to the host
|
||||
given in the URL, with fallback to earlier HTTP versions if needed.
|
||||
given in the URL, with fallback to lower HTTP versions if needed.
|
||||
|
||||
## CURL_HTTP_VERSION_3ONLY
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue