Adding support for no_proxy env variable #1693
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
August 7, 2018 10:02
* Adds support for the no_proxy environment variable commonly available with programs supporting the http_proxy/https_proxy environment variables. * Adds tests to test the no_proxy environment variable.
* Adds documentation to README.md for the supported, conventional http_proxy, https_proxy, and no_proxy environment variables.
|
@emilyemorehouse Added the documentation 🙂 |
emilyemorehouse
approved these changes
Aug 7, 2018
|
I have a no_proxy entry in the pattern |
This was referenced Aug 13, 2019
|
@LeeAdcock |
This was referenced Aug 29, 2019
This was referenced Sep 22, 2019
This was referenced Oct 16, 2019
This was referenced Oct 26, 2019
Closed
Closed
This was referenced Mar 25, 2020
This was referenced Apr 1, 2020
This was referenced Apr 9, 2020
This was referenced Apr 16, 2020
This was referenced Apr 25, 2020
HellRestaurant
pushed a commit
to HellRestaurant/cypress-testrail-reporter
that referenced
this pull request
Oct 1, 2020
Update axios to 0.20.0 to fix issue where NO_PROXY environment variable is being ignored (fix: axios/axios#1693)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit adds support for the
no_proxyenv variable (Issue #434 and on umbrella issue for 1.0.0). It looks like there's an open PR #565, however it has conflicts, adds an unnecessary dependency, and was created in 2016 and hasn't been merged yet. At the company where I work, we are behind a proxy and are having to work around this lack of functionality, and it seems like several people are in a similar situation, so it'd be nice to have this feature. 🙂