NO_PROXY doesn't work for IPv6 literals. #2353
Labels
Comments
|
Yes, seems like an accurate observation. Time to add a test case with an IPv6 numerical for this too... |
bagder
added a commit
that referenced
this issue
Mar 3, 2018
Reported-by: steelman on github Fixes #2353
|
It'd be great if you can just verify my patch in #2355. I'll try to add a test case for it before I merge anyway. |
|
I will verify it. You, however, may consider documenting the format of IPv6 entries in NO_PROXY, with or without square brackets. If I undetstand the patch brackets are required in NO_PROXY. I am not sure this is good.
|
|
Docs is good indeed. But no, the brackets are not used in the NO_PROXY list. They are however mandatory in the URL itself. |
|
Works for me (-: Thanks. How about updating docs/curl.1 too? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I use TOR as a proxy. TOR actually refuses to establish connection to localhost, so I set NO_PROXY
It enables connections to http://localhost and http://127.0.0.1 and does not work for http://[::1] at all.
Apparently the problem is caused by an assumption that a hostname cannot contain a colon.
The text was updated successfully, but these errors were encountered: