fix(proxy): handle WinINET IP wildcards - #309
Merged
seanmonstar merged 2 commits intoAug 3, 2026
Merged
Conversation
seanmonstar
approved these changes
Aug 3, 2026
barjin
pushed a commit
to apify/hyper-util
that referenced
this pull request
Aug 4, 2026
Normalize IPv4 wildcard patterns returned by WinINET, such as 127.* and 192.168.*, into equivalent CIDR ranges before matching system proxy exclusions. Fixes hyperium/hyper#4128
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
2 participants
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.
Fixes hyperium/hyper#4128.
Normalize IPv4 wildcard patterns returned by WinINET, such as
127.*and192.168.*, into equivalent CIDR ranges before matching system proxy exclusions.Standard NO_PROXY parsing remains unchanged.
Tests: