Add IPv6 CIDR support to no_proxy handling #7148
Open
+71
−7
Conversation
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
Extend proxy bypass logic to correctly interpret IPv6 CIDR ranges defined in the no_proxy environment variable. Existing IPv4 and hostname behavior remains unchanged.
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.
Summary
This PR adds support for IPv6 CIDR ranges in the
no_proxyenvironmentvariable when determining proxy bypass behavior.
Motivation
While Requests already supports IPv4 CIDR ranges and exact IPv6 matches,
IPv6 CIDR ranges were not handled, leading to inconsistent behavior in
IPv6-enabled environments.
Testing