1# Items to be removed from future curl releases 2 3If any of these deprecated features is a cause for concern for you, please 4email the 5[curl-library mailing list](https://lists.haxx.se/listinfo/curl-library) 6as soon as possible and explain to us why this is a problem for you and 7how your use case cannot be satisfied properly using a workaround. 8 9## NSS 10 11We remove support for building curl with the NSS TLS library in August 2023. 12 13- There are few users left who use curl+NSS 14- NSS has few users outside of curl as well (primarily Firefox) 15- NSS is harder than ever to find documentation for 16- NSS was always "best" used with Red Hat Linux when they provided additional 17 features on top of the regular NSS that is not shipped by the vanilla library 18 19Starting in 7.82.0, building curl to use NSS configure requires the additional 20flag `--with-nss-deprecated` in an attempt to highlight these plans. 21 22## gskit 23 24We remove support for building curl with the gskit TLS library in August 2023. 25 26- This is a niche TLS library, only running on some IBM systems 27- no regular curl contributors use this backend 28- no CI builds use or verify this backend 29- gskit, or the curl adaption for it, lacks many modern TLS features making it 30 an inferior solution 31- build breakages in this code take weeks or more to get detected 32- fixing gskit code is mostly done "flying blind" 33 34## mingw v1 35 36We remove support for building curl with the original legacy mingw version 1 37in September 2023. 38 39During the deprecation period you can enable the support with the configure 40option `--with-mingw1-deprecated`. 41 42mingw version 1 is old and deprecated software. There are much better and 43still support build environments to use to build curl and other software. For 44example [MinGW-w64](https://www.mingw-w64.org/). 45 46## space-separated `NOPROXY` patterns 47 48When specifying patterns/domain names for curl that should *not* go through a 49proxy, the curl tool features the `--noproxy` command line option and the 50library supports the `NO_PROXY` environment variable and the `CURLOPT_NOPROXY` 51libcurl option. 52 53They all set the same list of patterns. This list is documented to be a set of 54**comma-separated** names, but can also be provided separated with just 55space. The ability to just use spaces for this has never been documented but 56some users may still have come to rely on this. 57 58Several other tools and utilities also parse the `NO_PROXY` environment 59variable but do not consider a space to be a valid separator. Using spaces for 60separator is probably less portable and might cause more friction than commas 61do. Users should use commas for this for greater portability. 62 63curl will remove the support for space-separated names in July 2024. 64 65## past removals 66 67 - Pipelining 68 - axTLS 69 - PolarSSL 70 - NPN 71 - Support for systems without 64 bit data types 72