{"version":"2.1.90","anchor":"parent-proxy-configuration","canonical_anchor":"parent-proxy-configuration","heading":"Parent Proxy Configuration","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.90\/e\/parent-proxy-configuration","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.90","markdown":"### Parent Proxy Configuration\n\n**What**\n\nThe sandbox proxy can now route outbound traffic through an upstream (parent) HTTP proxy, enabling use in corporate environments with mandatory egress proxies.\n\n**Details**\n\n- Configured via the `network.parentProxy` setting, with sub-keys for `http`, `https`, and `noProxy`\n- Falls back to standard `HTTP_PROXY` \/ `HTTPS_PROXY` \/ `NO_PROXY` environment variables when the setting is not explicitly configured\n- `NO_PROXY` supports hostname suffixes, wildcard `*`, and CIDR ranges (both IPv4 and IPv6)\n- Localhost and loopback addresses always bypass the parent proxy\n- CONNECT tunneling through the parent proxy for HTTPS traffic, with proper authentication (Basic auth from proxy URL credentials)\n- Hop-by-hop headers are stripped when forwarding through the proxy\n- Logs configured proxy URLs at startup: `Parent proxy configured: http=... https=...`\n\n**Evidence**\n\nParent proxy routing logic (search for `\"Upstream HTTP proxy for outbound connections\"` and `\"Parent proxy configured\"`)"}