5 ms·
Great idea but the 'Fahrenheit 451' allusion is against the HTTP spec. 400-499 is for client errors. A client requesting a resource from site that can't show it
by nailer 11y ago
Great idea but the 'Fahrenheit 451' allusion is against the HTTP spec. 400-499 is for client errors. A client requesting a resource from site that can't show it for legal reasons is not the client's fault.
- rocky1138 11y agoIt could be that the client is in a location where showing it is against censorship laws. In this case, the client is at fault.
- iLoch 11y agoAgreed. I think this would often be the case for returning a 451 as well.
- lnanek2 11y agoYes, they even talk about recommending to the user to use Onion instead, so that's definitely a case they are considering.
- JoshTriplett 11y agoIn particular, just as the body of a 404 or 403 response can provide information to the client about how to make the request successfully (e.g. "did you mean one of these?" or "you need to log in", respectively), the body of a 451 response could suggest what the client could do to make the request successfully (e.g. "please try again from a less broken jurisdiction or over a more secure path").
- shaggyfrog 11y agoI think it's appropriate for the context. In an Orwellian society, of course it's the user who is at fault for requesting something they "shouldn't"...
- mbrubeck 11y agoRFC 2616 describes the 4xx error codes as “Client Error - The request contains bad syntax or cannot be fulfilled.” In other words, the error has to do with the client’s request but it's not necessarily the client’s fault. For a similar example see the response code “410 Gone”: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.11 http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10...
- mnot 11y agoRFC2616 is obsolete, see http://httpwg.github.io/specs/rfc7231.html http://httpwg.github.io/specs/rfc7231.html (and friends, as referenced).
- simoncion 11y agoThis is a better link: https://tools.ietf.org/html/rfc7231 https://tools.ietf.org/html/rfc7231 The IETF's HTML RFC generator makes really nice documents.
- mnot 11y agoI'm sorry, you just broke my sarcasm detector :) FWIW, the RFC Editor is working on modernising the RFC format -- we'll even have non-ASCII characters soon! https://www.rfc-editor.org/rse/format-faq/ https://www.rfc-editor.org/rse/format-faq/
- simoncion 11y agoI expect that your sarcasm detector was already broken. The IETF generator links to plain-text and PDF versions of the RFC, diffs between the current version and previous versions of the document, errata applicable to the RFC, and uses a fixed-width font. These are all nice properties.
- nailer 11y agoFormatting output for specific presentation devices (78 char wide screens) requiring a Chrome extension or a PDF for readability isn't my personal idea of 'nice'.
- simoncion 11y agoOver the years, I've come to understand that -once you surpass the "comprehensibility/legibility" threshold- "readability" is no less subjective than "beauty", "pleasantness", or "good music". So. I'm glad that you're not in charge of the IETF's HTML RFC output. :)
- morgante 11y agoAs the article notes, this is often replacing cases where a 403 error would instead be served. This is because censorship is almost never global—instead, it's because something about your request (often, your country of origin) forbids you from receiving it. In that context, 451 makes perfect sense.
- JoshTriplett 11y agoThat seems less likely to arise in practice, though. A server should only respect such requests from a jurisdiction that can threaten the server; thus, "we can't serve you this because your jurisdiction forbids it (but ours doesn't)" should almost never arise. The only potentially useful case there seems like "if we didn't remove this, your jurisdiction would block our entire site, eliminating the opportunity for us to tell you what has gone wrong and how to fix it". "We can't serve you this because our jurisdiction forbids it" seems likely to arise more often. That said, I also don't think the 4xx/5xx distinction matters as much here as the evocative implication of using 451 specifically.
- morgante 11y ago> "we can't serve you this because your jurisdiction forbids it (but ours doesn't)" should almost never arise. Uh, it happens all the time. In fact, it's by far the most frequent kind of censorship. From TFA: - https://en.wikipedia.org/wiki/Censorship_of_Facebook https://en.wikipedia.org/wiki/Censorship_of_Facebook - https://en.wikipedia.org/wiki/Censorship_by_Google https://en.wikipedia.org/wiki/Censorship_by_Google - https://en.wikipedia.org/wiki/Censorship_of_Twitter https://en.wikipedia.org/wiki/Censorship_of_Twitter Most major web services are based in a country with relatively lax censorship laws but still comply with censorship laws in other jurisdictions.
- thescriptkiddie 11y agoWhile this happens all the time, I would argue that it is not a good use case for HTTP 451. A better approach would be to just serve the content. If a country wants to censor your content they can do it the hard way. Don't help the bad guys.
- exo762 11y agoNor it is server's fault. Do we have http status code group for reality flaws?
- mnot 11y agoStatus code ranges are less about fault than they are about determining whether the client can retry the request without changing it. 5xx means that the client can, because there's a chance repeating the request will succeed. 4xx means the client shouldn't, because it needs to change in some fashion before it will work. This is so that clients that don't understand a specific status code can fall back to the more generic x00 code and still behave sensibly.
- nchelluri 11y agoI think that in practice 4xx is (and ought to be) any error other than a fatal server side error. I really dislike it when, e.g., Ruby HTTP client libraries treat any non 2xx-3xx response as an exception. If I'm wrong about this usage, like, say I have a REST endpoint that, when the client doesn't send bad data, but a request fails for some reason (upstream service rejected request), what kind of code is my endpoint supposed to return? (I would say 4xx, and leave it at that, getting rid of the "client" part of "client error", and leaving 5xx for something like ISE, fatal error "maybe ain't your fault, or at all under your control, client-man!" But I'm happy to learn more.)