Repository navigation
Allow dedicated listeners for managed network proxies - #45463
Merged
copyberry[bot] merged 1 commit intoSep 14, 2026
Merged
copyberry[bot] merged 1 commit into
copyberry[bot] merged 1 commit into
Conversation
## Why Sandboxes that enforce endpoint access directly need dedicated loopback proxy ports instead of shared SID-attributed ingress. ## What changed Expose `ManagedProxyRouting` through `NetworkProxyBuilder::managed_proxy_routing`. Selecting `DedicatedListeners` reserves per-proxy loopback listeners on Windows as well as other platforms. Keep `SharedIngress` as the default and include the routing mode in proxy equality. ## Testing Add regression coverage for distinct loopback endpoints, sandbox port metadata, and HTTP and SOCKS allow/deny policy enforcement. On Windows, verify that dedicated routing requires no restricting SID and omits the shared-ingress proxy-port environment variable. GitOrigin-RevId: e198891bef1d089f9492d2982505a2d6bb002a74
copyberry
Bot
force-pushed
the
copyberry/codex-internal-to-codex-oss/e198891bef1d089f9492d2982505a2d6bb002a74
branch
from
September 14, 2026 16:52
5789a63 to
99b3ab2
Compare
copyberry
Bot
deleted the
copyberry/codex-internal-to-codex-oss/e198891bef1d089f9492d2982505a2d6bb002a74
branch
September 14, 2026 16:52
This branch was successfully deployed
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
10 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.
Allow dedicated listeners for managed network proxies
Why
Sandboxes that enforce endpoint access directly need dedicated loopback proxy ports instead of shared SID-attributed ingress.
What changed
Expose
ManagedProxyRoutingthroughNetworkProxyBuilder::managed_proxy_routing. SelectingDedicatedListenersreserves per-proxy loopback listeners on Windows as well as other platforms. KeepSharedIngressas the default and include the routing mode in proxy equality.Testing
Add regression coverage for distinct loopback endpoints, sandbox port metadata, and HTTP and SOCKS allow/deny policy enforcement. On Windows, verify that dedicated routing requires no restricting SID and omits the shared-ingress proxy-port environment variable.