A New HTTP Status Code for Legally-restricted Resources
tools.ietf.orgthis is a prime example of a maliciously edited title. it shows as "Error Code 451: an HTTP error for censorship" at the moment which is what brsata submitted I guess.
the actual title of the draft is " A New HTTP Status Code for Legally-restricted Resources".
there can be many reasons, most prominently oldschool broadcasting licenses, that do not allow for global distribution. those have nothing to do with censorship.
Not maliciously edited but you are right. I've edited title to "A New HTTP Status Code for Legally-restricted Resources", the original title. "Error Code 451: an HTTP error for censorship" is from boingboing.net: http://boingboing.net/2012/06/13/error-code-451-an-http-erro...
"Maliciously" was a word too strong, sorry.
As a side note to this, the author of the draft aknowledges a blog post Terrence Eden which do call for the creation of a HTTP code for censorship
Link: http://shkspr.mobi/blog/index.php/2012/06/there-is-no-http-c...
Good point. That would definitely be a good use for this code, and the real title is more politically correct. In the poster's defense, though, the tone of the document really does seem biased toward government censorship activities.
Discussion from two days ago: http://news.ycombinator.com/item?id=4099751
I'm not at all familiar with IETF and the creation of new codes. What are the chances this becomes a real, widely used HTTP code?
Appendix A -- "Thanks to Ray Bradbury"
The returned error code value is a reference to "Farenheit 451."