{"version":"2.1.90","anchor":"proxy-error-handling","canonical_anchor":"proxy-error-handling","heading":"Proxy Error Handling","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.90\/e\/proxy-error-handling","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.90","markdown":"### Proxy Error Handling\n\nThe sandbox proxy now provides more specific error messages for connection failures:\n\n- `\"CONNECT handshake timed out\"` \u2014 timeout during proxy CONNECT\n- `\"Proxy closed during CONNECT handshake\"` \u2014 premature close\n- `\"Proxy refused CONNECT: ...\"` \u2014 non-2xx response from proxy\n- `\"CONNECT response header too large\"` \u2014 headers exceeding 16KB\n- `\"Denying malformed host: ...\"` \/ `\"Rejecting malformed SOCKS host: ...\"` \u2014 input validation\n- `\"Invalid destination host for CONNECT\"` \/ `\"Invalid destination port\"` \u2014 bad target validation\n- `\"Invalid parent proxy URL, ignoring: ...\"` \u2014 misconfigured parent proxy URL\n- `\"unsupported scheme or empty host\"` \u2014 bad proxy URL scheme\n\n**Evidence**\n\nCONNECT tunnel error handling (search for `\"CONNECT handshake timed out\"` and `\"Proxy refused CONNECT\"`)"}