older -> lower, version -> v

This commit is contained in:
Viktor Szakats 2026-05-26 20:32:53 +02:00
parent 3239116b53
commit 8f38830365
No known key found for this signature in database
11 changed files with 25 additions and 28 deletions

View file

@ -75,10 +75,10 @@ Local crypto gets removed in October 2026.
- winbuild build system (removed in 8.17.0)
- Windows CE (removed in 8.18.0)
- Support for Visual Studio 2008 (removed in 8.18.0)
- OpenSSL 1.1.1 and older (removed in 8.18.0)
- OpenSSL 1.1.1 and lower (removed in 8.18.0)
- Support for Windows XP (removed in 8.19.0)
- OpenSSL-QUIC (removed in 8.19.0)
- CMake 3.17 and older (removed in 8.20.0)
- CMake 3.17 and lower (removed in 8.20.0)
- RTMP (removed in 8.20.0)
- SMB (became opt-in in 8.20.0)
- NTLM (became opt-in in 8.20.0)

View file

@ -44,7 +44,7 @@ completely. Sometimes you may need to explicitly select an SSL version to
use when connecting to make the connection succeed.
An additional complication can be that modern SSL libraries sometimes are
built with support for older SSL and TLS versions disabled.
built with support for lower SSL and TLS versions disabled.
All versions of SSL and the TLS versions before 1.2 are considered insecure
and should be avoided. Use TLS 1.2 or greater.

View file

@ -571,7 +571,7 @@ See [curl issue 5396](https://github.com/curl/curl/issues/5396)
Certain stupid networks and middle boxes have a problem with SSL handshake
packets that are within a certain size range because how that sets some bits
that previously (in older TLS version) were not set. The `clienthello`
that previously (in lower TLS version) were not set. The `clienthello`
extension adds padding to avoid that size range.
- https://datatracker.ietf.org/doc/html/rfc7685

View file

@ -27,9 +27,9 @@ This option allows a user to avoid using the Alt-Svc method of upgrading to
HTTP/3 when you know or suspect that the target speaks HTTP/3 on the given
host and port.
When asked to use HTTP/3, curl issues a separate attempt to use older HTTP
When asked to use HTTP/3, curl issues a separate attempt to use lower HTTP
versions with a slight delay, so if the HTTP/3 transfer fails or is slow, curl
still tries to proceed with an older HTTP version. The fallback performs the
still tries to proceed with a lower HTTP version. The fallback performs the
regular negotiation between HTTP/1 and HTTP/2.
Use --http3-only for similar functionality *without* a fallback.