| CARVIEW |
Select Language
HTTP/2 200
date: Mon, 14 Jul 2025 14:48:14 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 95f1d1dda9e5dfa6-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 2616 » RFC Editor
Search RFCs
RFC 2616
Hypertext Transfer Protocol -- HTTP/1.1, June 1999
- File formats:
- Status:
- DRAFT STANDARD
- Obsoletes:
- RFC 2068
- Obsoleted by:
- RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235
- Updated by:
- RFC 2817, RFC 5785, RFC 6266, RFC 6585
- Authors:
- R. Fielding
J. Gettys
J. Mogul
H. Frystyk
L. Masinter
P. Leach
T. Berners-Lee - Stream:
- IETF
- Source:
- http (app)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC2616
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 2616
Abstract
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]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us