New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
foo.bar.domain.com
shouldn't be proxied if no_proxy has .domain.com
item
#2160
Comments
I just found that there is already a PR to solve this. #1880 |
I would like to ask the original author (@chancedickson ) for the rationale behind this comparison. I also found this problem and I'm interested in seeing if this is by design. |
We also noticed today that Axios will proxy |
So Axios understands suffixes (without *) - |
Yes it doesn't work with wildcard e.g.
Over here: Line 113 in 42eb9df
|
0.19.1 already solved this problem, I'm closing this issue. |
I agree with the above, so I will raise another one with the wildcard issue |
I have raised #2864 |
Describe the bug
foo.bar.domain.com
would still be proxied ifno_proxy
env has.domain.com
item.Related code is here:
axios/lib/adapters/http.js
Line 122 in fd0c959
foo.bar.domain.com
has 3 dots. On the contrary,.domain.com
has 2 dots. So it will not match.request uses
indexOf
, which supports this.Wondering that is this a but or it's a original designing. If it's a bug, I'm willing to make a PR.
To Reproduce
set system envariable:
Expected behavior
Shouldn't proxied.
Environment:
The text was updated successfully, but these errors were encountered: