The new status code is 451 with the description set as “Unavailable for Legal Reasons” on the page.
They do request that ISPs who are using this status code also include details about why it has been removed, although I can see it being used often without the explanation.
Responses using this status code SHOULD include an explanation, in the response body, of the details of the legal demand: the party making it, the applicable legislation or regulation, and what classes of person and resource it applies to. For example:
HTTP/1.1 451 Unavailable For Legal Reasons
Link: <https://spqr.example.org/legislatione>; rel=”blocked-by”
Content-Type: text/html<html>
<head><title>Unavailable For Legal Reasons</title></head>
<body>
<h1>Unavailable For Legal Reasons</h1>
<p>This request may not be serviced in the Roman Province
of Judea due to the Lex Julia Majestatis, which disallows
access to resources hosted on servers deemed to be
operated by the People’s Front of Judea.</p>
</body>
</html>
In a blog post by Mark Nottingham he says that it became apparent that there would be benefits from adding a new status code, even with the concern that they are limited to the 400-499 range, and once they are gone, they have no more in the 4xx range. But he felt it was more important as censorship issues become more prevalent as well as sites wanting the ability to crawl and discover pages that have been removed via legal takedowns and displaying a specific status code that represents that.
More importantly, we started to hear from members of the community that they wanted to be able to discover instances of censorship in an automated fashion. For example, Lumen (previously, Chilling Effects) and Article19 expressed interest in being able to spider the Web to look for the 451 status code, so they could catalogue censorship.
He also mentions that some sites have begun to adopt the 451 status code experimentally.
They interestingly make a case where a party might not want a case of a page being taken offline as a result of legal action.
5. Security Considerations
Clients cannot rely upon the use of the 451 status code. It is
possible that certain legal authorities might wish to avoid
transparency, and not only demand the restriction of access to
certain resources, but also avoid disclosing that the demand was
made.
So it is possible if the use of 451 becomes standard, that some legal takedowns might request that a 451 status code not be used, specifically because some might deem it too transparent.
Previously, companies were usually using the 403 Forbidden status code, although it didn’t exactly fit a scenario where a site or page was removed for legal reasons.
H/T Eric Wu
Jennifer Slegg
Latest posts by Jennifer Slegg (see all)
- 2022 Update for Google Quality Rater Guidelines – Big YMYL Updates - August 1, 2022
- Google Quality Rater Guidelines: The Low Quality 2021 Update - October 19, 2021
- Rethinking Affiliate Sites With Google’s Product Review Update - April 23, 2021
- New Google Quality Rater Guidelines, Update Adds Emphasis on Needs Met - October 16, 2020
- Google Updates Experiment Statistics for Quality Raters - October 6, 2020