All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
451 Unavailable for Legal Reasons
So an Amazon employee (Tim Bray is the name of the fella) invented an new error status code with the number "451" and the description "Unavailable for Legal Reasons".
RFC: https://datatracker.ietf.org/doc/draft-ietf-httpbis-legally-restricted-status/?include_text=1
And it looks like the IESG gremium of the IETF approved it. Currently an official and final version of the RFC is being written and is to be published soon.
Approval: https://datatracker.ietf.org/doc/draft-ietf-httpbis-legally-restricted-status/ballot/
Imho this is a funny code I'd like to see all on all Youtube pages that have been blocked due to Gema and et cetera. Would be fun. It also can be seen as a censorship sign.
Your thoughts?
Source: http://m.heise.de/newsticker/meldung/Neuer-Status-Code-451-zeigt-Zensur-an-3052138.html
Comments
My suggestion:
Error code 666
Error:
Piss off. We don't like you.
I'm not sure if you can create a custom error code in nginx? Or would clients mistranslate it?
Or would it crash nginx?
I don't think it would crash anything.
Mistranslation would only happen if clients have saved 451 as something else I suppose.
After all a error/status is a HTML page plus a header with the number of the status code and its description.
Rest depends on how clients interpret it.
That's perfect for those who are trying to view Hulu from Europe
I use "666 Something's fucky!" in one of my things. Probably not recommended but hasn't caused any problems.
Already on it.
Now sending code 451 for all my websites running PHP with http_response_code function. (ex:
http_response_code(451);)Clients look at the first digit, so wouldn't mistranslate.
666 would probably fall back to 200.
As @Hidden_Refuge said, it's a mere indication, it doesn't "do" anything so to say
WoW, we still need something just for our Gema, 451 wont be enought.
Maybe (GMA) 462 - You've been GEMAed! or (GEM) 436 - You've been GEMAed! or something like that.
T9 times lol but both 462 and 436 are free.
I don't necessarily see this as a bad thing. Could be convenient for search engines, crawlers, etc.
I agree. I think it makes a ton of sense. Though I'm curious if this will be used in cases like a DMCA violation? Or is this more simply restricted content, such as Twitter being blocked in China?
We use HTTP 418 "I'm a teapot" on our site so 451 seems almost normal
It's odd to have a HTTP standard code based on a name of a fantasy book...
Fantasy? I saw the movie when it first came out and I didn't think it was a fantasy, even back then.
Takedown + soapboxing is still takedown, so I think it's a splendid idea.
This message not an official communication of the People's Front of Judea.