{"version":"2.1.304","anchor":"sandbox-proxy-deny-responses-can-use-a-custom-status-and-an","canonical_anchor":"sandbox-proxy-deny-responses-can-use-a-custom-status-and-an","heading":"Sandbox network refusals can use other status codes and error headers","tier":"internal","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/sandbox-proxy-deny-responses-can-use-a-custom-status-and-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Sandbox network refusals can use other status codes and error headers\n\nWhen the sandbox proxy blocks a request, the reply can now use a status other than 403 and a different error header\n\n**Unclear.** Which blocked requests now get a status other than 403 or a different header is not stated.\n\n**What**\n\nWhen the sandbox's network proxy blocks a request, it sends back an error reply. That reply used to be fixed: status 403 with an `X-Proxy-Error` header. The status can now be set, still 403 by default, and the error header's name and value are worked out case by case.\n\n**Why**\n\nIf something you run checks for a 403 or the `X-Proxy-Error` header to spot a blocked request, it may now see a different reply.\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}