4 ms·

RFC2616 is obsolete, see http://httpwg.github.io/specs/rfc7231.html http://httpwg.github.io/specs/rfc7231.html (and friends, as referenced).

• simoncion 11y ago
  This 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 ago
    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/ https://www.rfc-editor.org/rse/format-faq/
    • simoncion 11y ago
      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.
      • nailer 11y ago
        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'.
        • simoncion 11y ago
          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. :)