HTTP/1.1
This specification has been revised 20 times since RFC 2068 (1997). Each document below formally obsoleted the one before it; the versions still in force are listed first.
Revision timeline
- RFC 2068 (1997)
- RFC 2069 (1997)
- RFC 2145 (1997)
- RFC 2616 (1999)
- RFC 2617 (1999)
- RFC 2818 (2000)
- RFC 7230 (2014)
- RFC 7231 (2014)
- RFC 7232 (2014)
- RFC 7233 (2014)
- RFC 7234 (2014)
- RFC 7235 (2014)
- RFC 7238 (2014)
- RFC 7538 (2015)
- RFC 7615 (2015)
- RFC 7616 (2015)
- RFC 7617 (2015)
- RFC 7694 (2015)
- RFC 9110 (2022)
- RFC 9111 (2022)
- RFC 9112 (2022) ✓
Current versions — implement against these
- RFC 7616HTTP Digest Access AuthenticationCurrentSeptember 2015proposed standard
- RFC 7617The 'Basic' HTTP Authentication SchemeCurrentSeptember 2015proposed standard
- RFC 9110HTTP SemanticsCurrentJune 2022internet standard
- RFC 9111HTTP CachingCurrentJune 2022internet standard
- RFC 9112HTTP/1.1UpdatedJune 2022internet standard
Superseded versions — historical reference only
- RFC 2068Hypertext Transfer Protocol -- HTTP/1.1ObsoletedJanuary 1997proposed standardreplaced by RFC2616
- RFC 2069An Extension to HTTP : Digest Access AuthenticationObsoletedJanuary 1997proposed standardreplaced by RFC2617
- RFC 2145Use and Interpretation of HTTP Version NumbersObsoletedMay 1997informationalreplaced by RFC7230
- RFC 2616Hypertext Transfer Protocol -- HTTP/1.1ObsoletedJune 1999draft standardreplaced by RFC7230, RFC7231, RFC7232, RFC7233, RFC7234, RFC7235
- RFC 2617HTTP Authentication: Basic and Digest Access AuthenticationObsoletedJune 1999draft standardreplaced by RFC7235, RFC7615, RFC7616, RFC7617
- RFC 2818HTTP Over TLSObsoletedMay 2000informationalreplaced by RFC9110
- RFC 7230Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and RoutingObsoletedJune 2014proposed standardreplaced by RFC9110, RFC9112
- RFC 7231Hypertext Transfer Protocol (HTTP/1.1): Semantics and ContentObsoletedJune 2014proposed standardreplaced by RFC9110
- RFC 7232Hypertext Transfer Protocol (HTTP/1.1): Conditional RequestsObsoletedJune 2014proposed standardreplaced by RFC9110
- RFC 7233Hypertext Transfer Protocol (HTTP/1.1): Range RequestsObsoletedJune 2014proposed standardreplaced by RFC9110
- RFC 7234Hypertext Transfer Protocol (HTTP/1.1): CachingObsoletedJune 2014proposed standardreplaced by RFC9111
- RFC 7235Hypertext Transfer Protocol (HTTP/1.1): AuthenticationObsoletedJune 2014proposed standardreplaced by RFC9110
- RFC 7238The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)ObsoletedJune 2014experimentalreplaced by RFC7538
- RFC 7538The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)ObsoletedApril 2015proposed standardreplaced by RFC9110
- RFC 7615HTTP Authentication-Info and Proxy-Authentication-Info Response Header FieldsObsoletedSeptember 2015proposed standardreplaced by RFC9110
- RFC 7694Hypertext Transfer Protocol (HTTP) Client-Initiated Content-EncodingObsoletedNovember 2015proposed standardreplaced by RFC9110
This lineage is derived automatically from the “obsoletes” relationships recorded in the public RFC Editor index — no editorial judgement is applied to the ordering. The most recent document in the chain is RFC 9112 (June 2022).