RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235.
Current document in this lineage: RFC 7616 — HTTP Digest Access Authentication; RFC 7617 — The 'Basic' HTTP Authentication Scheme; RFC 9110 — HTTP Semantics; RFC 9111 — HTTP Caching; RFC 9112 — HTTP/1.1
In plain English — editorial summary, not part of the RFC
RFC 2616 was the long-standing definition of HTTP/1.1 — methods, status codes, headers, caching and persistent connections — and it is the RFC most often cited in older code and documentation. It has been obsoleted: HTTP/1.1 was re-specified in 2014 as RFCs 7230–7235, and again in 2022 as RFCs 9110–9112. Cite the current documents for new work; RFC 2616 remains useful only as a historical reference.
Original abstract from the RFC
HTTP has been in use by the World-Wide Web global information initiative since 1990. This specification defines the protocol referred to as "HTTP/1.1", and is an update to RFC 2068. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2616
- Published
- June 1999
- Authors
- R. Fielding; J. Gettys; J. Mogul; H. Frystyk; L. Masinter; P. Leach; T. Berners-Lee
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 176
- Also known as
- —
- Obsoletes:
- RFC 2068
Topics
Standards lineage
This document is one revision in a chain of 21 RFCs, each formally replacing the one before it.
- 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) ✓
Referenced by
10 later RFCs formally update or obsolete part of this document.
- RFC 2817Upgrading to TLS Within HTTP/1.1Updated
May 2000
- RFC 5785Defining Well-Known Uniform Resource Identifiers (URIs)Obsoleted
April 2010
- RFC 6266Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)Current
June 2011
- RFC 6585Additional HTTP Status CodesCurrent
April 2012
- RFC 7230Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and RoutingObsoleted
June 2014
- RFC 7231Hypertext Transfer Protocol (HTTP/1.1): Semantics and ContentObsoleted
June 2014
- RFC 7232Hypertext Transfer Protocol (HTTP/1.1): Conditional RequestsObsoleted
June 2014
- RFC 7233Hypertext Transfer Protocol (HTTP/1.1): Range RequestsObsoleted
June 2014
- RFC 7234Hypertext Transfer Protocol (HTTP/1.1): CachingObsoleted
June 2014
- RFC 7235Hypertext Transfer Protocol (HTTP/1.1): AuthenticationObsoleted
June 2014
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2660The Secure HyperText Transfer ProtocolCurrent
August 1999
- RFC 2617HTTP Authentication: Basic and Digest Access AuthenticationObsoleted
June 1999
- RFC 2594Definitions of Managed Objects for WWW ServicesCurrent
May 1999
- RFC 2965HTTP State Management MechanismObsoleted
October 2000
- RFC 2227Simple Hit-Metering and Usage-Limiting for HTTPCurrent
October 1997
- RFC 3253Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning)Current
March 2002
- RFC 1866Hypertext Markup Language - 2.0Obsoleted
November 1995
- RFC 2585Internet X.509 Public Key Infrastructure Operational Protocols: FTP and HTTPCurrent
May 1999
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?