27c9b375f6
curl drops support for TLS libraries without TLS 1.3 capability after May 2025. It requires that a curl build using the library should be able to negotiate and use TLS 1.3, or else it is not good enough. We support a vast amount of other TLS libraries that are likely to satisfy users better. Closes #13544
1.8 KiB
Items to be removed from future curl releases
If any of these deprecated features is a cause for concern for you, please email the curl-library mailing list as soon as possible and explain to us why this is a problem for you and how your use case cannot be satisfied properly using a workaround.
TLS libraries without 1.3 support
curl drops support for TLS libraries without TLS 1.3 capability after May 2025.
It requires that a curl build using the library should be able to negotiate and use TLS 1.3, or else it is not good enough.
As of May 2024, the libraries that need to get fixed to remain supported after May 2025 are: BearSSL and Secure Transport.
space-separated NOPROXY patterns
When specifying patterns/domain names for curl that should not go through a
proxy, the curl tool features the --noproxy command line option and the
library supports the NO_PROXY environment variable and the CURLOPT_NOPROXY
libcurl option.
They all set the same list of patterns. This list is documented to be a set of comma-separated names, but can also be provided separated with just space. The ability to just use spaces for this has never been documented but some users may still have come to rely on this.
Several other tools and utilities also parse the NO_PROXY environment
variable but do not consider a space to be a valid separator. Using spaces for
separator is probably less portable and might cause more friction than commas
do. Users should use commas for this for greater portability.
curl removes the support for space-separated names in July 2024.
past removals
- Pipelining
- axTLS
- PolarSSL
- NPN
- Support for systems without 64 bit data types
- NSS
- gskit
- mingw v1
- NTLM_WB