Honor NO_PROXY="*" in Gem::Request::ConnectionPools - #9798
Merged
Conversation
curl and net-http-persistent treat a "*" entry as bypassing the proxy for every host, and Bundler's fetcher already honors it, but no_proxy? never matched it, so gem commands kept using the proxy. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Setting
NO_PROXY=*conventionally bypasses the proxy for every host. curl and net-http-persistent both honor it, and Bundler's fetcher honors it as well, butGem::Request::ConnectionPools#no_proxy?never matched a*entry, sogemcommands kept sending requests through the configured proxy. This treats a*entry as matching every host, so connections are built without proxy arguments.🤖 Generated with Claude Code