- From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
- Date: Mon, 20 Nov 2017 12:37:28 +0100
- To: ietf-http-wg@w3.org, hrpc@irtf.org
We have 451 for "unavailable for legal reasons" but I find <https://www.iana.org/assignments/http-status-codes/http-status-codes.xml> no code for "Unavailable because we have blocked access to this malware/phishing/bad site". Since there are many network middleboxes which do this sort of blocking, would it be a good idea to have a specific status code? The only draft I've found about this specific idea is <https://datatracker.ietf.org/doc/draft-lemon-tls-blocking-alert/>, but it is TLS-specific.
Received on Monday, 20 November 2017 11:38:02 UTC