Unclear Which blocked requests now get a status other than 403 or a different header is not stated.
What
When 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.
Why
If 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.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Which blocked requests now get a status other than 403 or a different header is not stated.