I Predict We Will be Using HTTP/1.1 451 Unavailable For Legal Reasons a Lot More in Future
I have the feeling that we will be using HTTP/1.1 451 Unavailable For Legal Reasons a lot more in the future. Anyone out there care to track the number of 451 status codes that emerge?
Join the DZone community and get the full member experience.Join For Free
I'm playing catch up with some of my news and information curation, something that always builds up when I travel. As part of my work I came across the RFC 7725, HTTP/1.1 451 Unavailable For Legal Reasons, providing an HTTP status code for use when access to a resource is denied as a consequence of legal demands.
The RFC states that, "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"—something I'm wondering if will even be possible in some situations.
Anyway, I wanted to make sure this HTTP status code was filed as part of my overall API Evangelist consciousness. I have the feeling that we will be using HTTP/1.1 451 Unavailable For Legal Reasons a lot more in the future, and want a reference point to link to. Hopefully, someone out there will be tracking the number of 451 status codes that emerge, so we can graph over time how many online resources go 451—I do not have the resources to do it.
Seems like it will be a pretty telling metric of the health of this online experiment, we are calling the web.
Published at DZone with permission of Kin Lane, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.