Adding NO_PROXY environment variable support. #228
Closed
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
boldfield
force-pushed
the
add-no-proxy
branch
from
f92e2af
to
f593e4d
Compare
boldfield
force-pushed
the
add-no-proxy
branch
from
f593e4d
to
f3e8d3c
Compare
|
Closing as duplicate; I searched issues for references to no_proxy and didn't find the open pull request (#221). Can't wait for that one to get merged =-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When defining a PROXY to connect to a public docker index, also allow the use of NO_PROXY to connect to private index.
Fixes issue #227