We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Could you add support for no_proxy environment variable please? so we are able to bypass proxy for specific url pattern?
Thanks
FYI: Similar request was made to axios as well but it yet not be part of official release - axios/axios#434
The text was updated successfully, but these errors were encountered:
This completely breaks gaxios on machines behind corporate proxies. Is there no way to work around this?
Sorry, something went wrong.
@csvan @jacklty could you describe the expected behavior of no_proxy with a bit more detail?
no_proxy
I gather you provide a list of domains that should not have https_proxy or http_proxy populated for them?
https_proxy
http_proxy
@bcoe precisely, it could look like this:
export no_proxy=localhost,127.0.0.0/8,::1,.mysub.mydomain.com,myotherdomain.net
Among others, node-fetch (at least seems) to respect it when used on its own.
node-fetch
feat: add support for no_proxy environment variable
9b60efd
Refs #69
sofisl
Successfully merging a pull request may close this issue.
Could you add support for no_proxy environment variable please? so we are able to bypass proxy for specific url pattern?
Thanks
FYI: Similar request was made to axios as well but it yet not be part of official release - axios/axios#434
The text was updated successfully, but these errors were encountered: