What's wrong with this entry?
The sandbox proxy can now route outbound traffic through an upstream (parent) HTTP proxy, enabling use in corporate environments with mandatory egress proxies.
- Configured via the
network.parentProxysetting, with sub-keys forhttp,https, andnoProxy - Falls back to standard
HTTP_PROXY/HTTPS_PROXY/NO_PROXYenvironment variables when the setting is not explicitly configured NO_PROXYsupports hostname suffixes, wildcard*, and CIDR ranges (both IPv4 and IPv6)- Localhost and loopback addresses always bypass the parent proxy
- CONNECT tunneling through the parent proxy for HTTPS traffic, with proper authentication (Basic auth from proxy URL credentials)
- Hop-by-hop headers are stripped when forwarding through the proxy
- Logs configured proxy URLs at startup:
Parent proxy configured: http=... https=...
Parent proxy routing logic (search for "Upstream HTTP proxy for outbound connections" and "Parent proxy configured")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.