[ALUG] If you are dealing with the HTTP protocol

[Andreas Tauscher]

RFC 2616 HTTP/1.1 is obsolete.

The HTTP/1.1 protocol was defined in RFC2616 in 1999 but since this time
the network changed and HTTP was "miss used" in many ways. For example:
WebDAV, AJAX and HTML5.
Many thing have been not clearly specified what caused frequently
compatibility problems or security issues.

The IETF started in 2008 the task force HTTPbis to redefine the HTTP
protocol. Now this is finished.

The now obsolete RFC 2616 is replaced by 6 RFCs:
RFC 7230- HTTP/1.1: Message Syntax and Routing – low-level message
parsing and connection management [1]
RFC 7231- HTTP/1.1: Semantics and Content – methods, status codes and
headers [2]
RFC 7232- HTTP/1.1: Conditional Requests – e.g., If-Modified-Since [3]
RFC 7233- HTTP/1.1: Range Requests – getting partial content [4]
RFC 7234- HTTP/1.1: Caching – browser and intermediary caches [5]
RFC 7235- HTTP/1.1: Authentication – a framework for HTTP authentication [6]

For an easy reference each of the new RFCs has a section "Changes from
RFC 2068" at the end.

Like Mark Nottingham (chair of the HTTPbis task force) advises in his
blog [7]:
"Don’t use RFC 2616. Delete it from your hard drives, bookmarks, and
burn (or responsibly recycle) any copies that are printed out."

Andreas

[1] http://tools.ietf.org/html/rfc7230
[2] http://tools.ietf.org/html/rfc7231
[3] http://tools.ietf.org/html/rfc7232
[4] http://tools.ietf.org/html/rfc7233
[5] http://tools.ietf.org/html/rfc7234
[6] http://tools.ietf.org/html/rfc7235
[7] https://www.mnot.net/blog/2014/06/07/rfc2616_is_dead