1<!-- 2Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al. 3 4SPDX-License-Identifier: curl 5--> 6 7# Items to be removed from future curl releases 8 9If any of these deprecated features is a cause for concern for you, please 10email the 11[curl-library mailing list](https://lists.haxx.se/listinfo/curl-library) 12as soon as possible and explain to us why this is a problem for you and 13how your use case cannot be satisfied properly using a workaround. 14 15## TLS libraries without 1.3 support 16 17curl drops support for TLS libraries without TLS 1.3 capability after May 182025. 19 20It requires that a curl build using the library should be able to negotiate 21and use TLS 1.3, or else it is not good enough. 22 23As of May 2024, the libraries that need to get fixed to remain supported after 24May 2025 are: BearSSL and Secure Transport. 25 26## space-separated `NOPROXY` patterns 27 28When specifying patterns/domain names for curl that should *not* go through a 29proxy, the curl tool features the `--noproxy` command line option and the 30library supports the `NO_PROXY` environment variable and the `CURLOPT_NOPROXY` 31libcurl option. 32 33They all set the same list of patterns. This list is documented to be a set of 34**comma-separated** names, but can also be provided separated with just 35space. The ability to just use spaces for this has never been documented but 36some users may still have come to rely on this. 37 38Several other tools and utilities also parse the `NO_PROXY` environment 39variable but do not consider a space to be a valid separator. Using spaces for 40separator is probably less portable and might cause more friction than commas 41do. Users should use commas for this for greater portability. 42 43curl removes the support for space-separated names in July 2024. 44 45## past removals 46 47 - Pipelining 48 - axTLS 49 - PolarSSL 50 - NPN 51 - Support for systems without 64 bit data types 52 - NSS 53 - gskit 54 - mingw v1 55 - NTLM_WB 56