{"version":"2.1.299","anchor":"upstream-proxy-responses-now-pass-through-a-headerstatus-ch","canonical_anchor":"upstream-proxy-responses-now-pass-through-a-headerstatus-ch","heading":"Sandbox network proxy now checks responses before passing them on","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/upstream-proxy-responses-now-pass-through-a-headerstatus-ch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Sandbox network proxy now checks responses before passing them on\n\nThe sandbox network proxy now checks each response's status and headers before forwarding it, rather than passing it straight through\n\n**Unclear.** What the new check rejects, and so which responses are now blocked, is not known.\n\n**What**\n\nThe sandbox is a restricted environment Claude Code can run commands in, and its network proxy is the go-between that handles their web traffic. When a response comes back from the outside server, the proxy used to forward its status and headers to the command and stream the rest straight through. It now runs the status and headers through a check first and forwards the response only if that check passes. This applies both to the normal proxy path and to the path that decrypts secure (TLS) traffic for inspection.\n\nErrors from the outside server are still logged as before.\n\n**Why**\n\nThis looks like a tightening of how the sandbox proxy handles responses, which matters if you rely on the sandbox to filter network access. Some responses that used to get through may now be stopped.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}