I wonder about the applicability of this status code to &#x27;friendly&#x27; blocking. In my workplace, as in many others, we have a web proxy that blocks certain requests for security or policy reasons. I would like it if the vendor implemented something like this for its capture page, as it&#x27;d make it easier to identify where requests are blocked and why in various logs. In particular, user-agents could tell the user when a request is blocked for this reason, which would be more robust than the HTML message it returns and would make help-desk operations a lot easier - &quot;this thing doesn&#x27;t work and I get a browser notice about blocking,&quot; instead of &quot;this thing doesn&#x27;t work&quot; and then having to dig through logs.<p>Just a thought about applications for this beyond the obvious (but less common in the US) state censorship - it can be seen as a technical help for making sure security and policy controls are clearly communicated to machines as well as people, which makes it easier to figure out when those controls are overbroad.