Repository navigation
feat(proxy): route proxy-native sessions through the standard env proxy - #169
Merged
Merged
Conversation
A runtime advertising INTROSPECTION_EGRESS_PROXY_NATIVE=1 gets the session credential as userinfo in HTTPS_PROXY and no egress URL, so the transports no longer rewrite requests to the egress when the flag is set or the egress URL is unset. Requests go through the forward proxy with Proxy-Authorization, honouring NO_PROXY and SSL_CERT_FILE. An https:// proxy is now verified with the same TLS context as origins, so an explicit verify= also covers it. Runtimes without the flag keep the legacy endpoint rewriting unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PsWKFYjGgYoYxChyJMtT8R
…-1ygb45 # Conflicts: # pyproject.toml # uv.lock
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 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.
Companion to introspection-org/introspection-cloud#3294 (proxy-native sandbox egress, Phase 5; design:
docs/design/sandbox-egress-proxy-native.mdthere).What
INTROSPECTION_EGRESS_PROXY_NATIVE=1is set, or there is noINTROSPECTION_EGRESS_URL, the httpx and httpx2 transports stop rewriting requests onto the egress. Requests go through the forward proxy withProxy-Authorizationfrom theHTTPS_PROXYuserinfo, honouringNO_PROXYandSSL_CERT_FILE.https://proxy is now verified with the same TLS context as the origins, so an explicitverify=also covers the proxy hop. This matters for the public egress listener that external sandboxes use.Testing
tests/rest/test_proxy.pyandtest_proxy_httpx.pycover these cases against local CONNECT proxies (tests/rest/proxy_servers.py), over bothhttp://andhttps://proxy forms with a test CA:NO_PROXY;uv.lockgains the test-only dependency.Follow-up
A separate Phase 6 branch deletes the legacy rewrite. It is held until no live runtime predates Phase 5.
🤖 Generated with Claude Code
https://claude.ai/code/session_01PsWKFYjGgYoYxChyJMtT8R
Generated by Claude Code