Issue #8329 - Add wildcard and CIDR pattern support to ProxyConfiguration include/exclude addresses #14205
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 #8329
Add pattern matching support for
ProxyConfiguration.Proxyincluded/excluded addresses:HostPortPatternclass supporting exact hostnames, wildcard prefix (*.example.com), wildcard suffix (internal.*), CIDR notation (192.168.0.0/16), and IP ranges (10.0.0.1-10.0.0.10)HostPortSetto work withIncludeExcludeSetfor pattern-based matchingProxyConfiguration.Proxyto useIncludeExcludeSet<String, HostPort>instead ofHashSet<String>@, paths/, middle wildcards)