romenskiy2012/curl
1
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2026-07-16 07:57:15 +03:00
Code Issues Projects Releases Packages Wiki Activity

noproxy: support for space-separated names is deprecated

Browse source 
To be removed in July 2024.

Assisted-by: Michael Osipov
Fixes #10209
Closes #10215
This commit is contained in:
Daniel Stenberg 2023-01-03 14:58:37 +01:00
parent bb393e521f
commit 7ad8a7ba9e
No known key found for this signature in database
GPG key ID: 5CC908FDB71E12C2
5 changed files with 88 additions and 44 deletions
Download patch file Download diff file Expand all files Collapse all files

19
docs/DEPRECATE.md
View file

@ -52,6 +52,25 @@ We remove support for building curl with the gskit TLS library in August 2023.
- build breakages in this code take weeks or more to get detected
- fixing gskit code is mostly done "flying blind"
## 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 will remove the support for space-separated names in July 2024.
## past removals
- Pipelining