News for hackers. Stuff that matters.
Re:Why 451? by mbrubeck on Saturday December 19, 2015 @06:37PM (#10765358)
RFC 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...

Re:Why 451? by mnot on Saturday December 19, 2015 @07:48PM (#10765565)
RFC2616 is obsolete, see http://httpwg.github.io/specs/rfc7231.html (and friends, as referenced).
Re:Why 451? by simoncion on Saturday December 19, 2015 @07:52PM (#10765571)
This is a better link: https://tools.ietf.org/html/rfc7231

The IETF's HTML RFC generator makes really nice documents.

Re:Why 451? by mnot on Saturday December 19, 2015 @08:03PM (#10765601)
I'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/

Re:Why 451? by simoncion on Saturday December 19, 2015 @08:16PM (#10765633)
I 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.

Re:Why 451? by nailer on Sunday December 20, 2015 @02:12PM (#10767921)
Formatting 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'.
Re:Why 451? by simoncion on Sunday December 20, 2015 @08:19PM (#10769055)
Over 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. :)