Hypertext Transfer Protocol -- HTTP/1.1
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 176
- 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]
- Publication Date
- 1999-06-01
- Status Note
- Draft Standard
- DOI
10.17487/RFC2616- Link
- https://doi.org/10.17487/RFC2616
- Author(s)
- Roy T. FieldingJim GettysJeffrey MogulHenrik NielsenLarry M MasinterPaul J. LeachTim Berners-Lee
- Keyword(s)
- HTTP, World Wide Web, Hypermedia
Latest version of IETF RFC 2616
Document Versions — IETF RFC 2616
-
▶ IETF RFC 2616 (1999-06-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Superseded by:
- IETF RFC 7230 [Superseded*]
- IETF RFC 7231 [Superseded*]
- IETF RFC 7232 [Superseded*]
- IETF RFC 7233 [Superseded*]
- IETF RFC 7234 [Superseded*]
- IETF RFC 7235 [Superseded*]
Amended by:
- IETF RFC 2817 [Active*]
- IETF RFC 5785 [Superseded*]
- IETF RFC 6266 [Active*]
- IETF RFC 6585 [Active*]
Bibliographic Reference(s)
- ANSI/INCITS X3.4:1986 (R1997) [Active]
- ISO/IEC 8859-1 [Active]
- Luotonen, A., "Tunneling TCP based protocols through Web proxy servers," Work in Progress. EXTERNAL
- S. Spero, "Analysis of HTTP Performance Problems," http://sunsite.unc.edu/mdma-release/http-prob.html . EXTERNAL
- Venkata N. Padmanabhan, and Jeffrey C. Mogul. "Improving HTTP Latency", Computer Networks and ISDN Systems, v. 28, pp. 25-35, Dec. 1995. Slightly revised version of paper in Proc. 2nd International WWW Conference '94: Mosaic and the Web, Oct. 1994, which is available at http://www.ncsa.uiuc.edu/SDG/IT94/Proceedings/DDay/mogul/HTTPLat ency.html . EXTERNAL
- Joe Touch, John Heidemann, and Katia Obraczka. "Analysis of HTTP Performance", <URL: http://www.isi.edu/touch/pubs/http-perf96/ >, ISI Research Report ISI/RR-98-463, (original report dated Aug. 1996), USC/Information Sciences Institute, August 1998. EXTERNAL
- Nielsen, H.F., Gettys, J., Baird-Smith, A., Prud'hommeaux, E., Lie, H., and C. Lilley. "Network Performance Effects of HTTP/1.1, CSS1, and PNG," Proceedings of ACM SIGCOMM '97, Cannes France, September 1997. EXTERNAL
- IETF RFC 821 [Superseded*]
- IETF RFC 822 [Superseded*]
- IETF RFC 850 [Superseded*]
- IETF RFC 959 [Active*]
- IETF RFC 977 [Superseded*]
- IETF RFC 1036 [Superseded*]
- IETF RFC 1123 [Active*]
- IETF RFC 1305 [Superseded*]
- IETF RFC 1436 [Active*]
- IETF RFC 1590 [Superseded*]
- IETF RFC 1630 [Active*]
- IETF RFC 1700 [Superseded*]
- IETF RFC 1737 [Active*]
- IETF RFC 1738 [Superseded*]
- IETF RFC 1766 [Superseded*]
- IETF RFC 1806 [Superseded*]
- IETF RFC 1808 [Superseded*]
- IETF RFC 1864 [Active*]
- IETF RFC 1866 [Superseded*]
- IETF RFC 1867 [Superseded*]
- IETF RFC 1900 [Active*]
- IETF RFC 1945 [Active*]
- IETF RFC 1950 [Active*]
- IETF RFC 1951 [Active*]
- IETF RFC 1952 [Active*]
- IETF RFC 2026 [Active*]
- IETF RFC 2045 [Active*]
- IETF RFC 2046 [Active, Amended*]
- IETF RFC 2047 [Active*]
- IETF RFC 2049 [Active*]
- IETF RFC 2068 [Superseded*]
- IETF RFC 2069 [Superseded*]
- IETF RFC 2076 [Active*]
- IETF RFC 2110 [Superseded*]
- IETF RFC 2119 [Active*]
- IETF RFC 2145 [Superseded*]
- IETF RFC 2183 [Active*]
- IETF RFC 2277 [Active*]
- IETF RFC 2279 [Superseded*]
- IETF RFC 2324 [Active*]
- IETF RFC 2396 [Superseded*]
- IETF RFC 2617 [Superseded*]
- TMC.WAIS.1.5.19900423 — 7 EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC2616.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 2616, Hypertext Transfer Protocol -- HTTP/1.1. Available at https://doi.org/10.17487/RFC2616
Snippet:
IETF RFC 2616, Hypertext Transfer Protocol -- HTTP/1.1. Available at https://doi.org/10.17487/RFC2616
HTML (ISO 690 compliant)
Preview:
IETF RFC 2616, Hypertext Transfer Protocol -- HTTP/1.1. Available at https://doi.org/10.17487/RFC2616
Snippet:
<span class="citation"><cite>IETF RFC 2616</cite>, Hypertext Transfer Protocol -- HTTP/1.1. Available at <a href="https://doi.org/10.17487/RFC2616" target="_blank" rel="noopener">https://doi.org/10.17487/RFC2616</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 2616, Hypertext Transfer Protocol -- HTTP/1.1
doi: 10.17487/RFC2616
url: https://doi.org/10.17487/RFC2616
doi: 10.17487/RFC2616
url: https://doi.org/10.17487/RFC2616
Snippet:
<li> <cite id="bib-rfc2616">IETF RFC 2616</cite>, Hypertext Transfer Protocol -- HTTP/1.1 <span class="doi">10.17487/RFC2616</span> </li>
Referenced By
- MPEG DASH: The Enabler Standard for Video Delivery over the Internet [Active]
- IETF draft-bormann-core-congestion-control-02 [Active*]
- IETF RFC 2617 [Superseded*]
- IETF RFC 2756 [Active*]
- IETF RFC 2781 [Active*]
- IETF RFC 2801 [Active*]
- IETF RFC 2817 [Active*]
- IETF RFC 2818 [Superseded*]
- IETF RFC 2828 [Superseded*]
- IETF RFC 2831 [Superseded*]
- IETF RFC 2854 [Active*]
- IETF RFC 2914 [Active*]
- IETF RFC 2965 [Superseded*]
- IETF RFC 3023 [Superseded*]
- IETF RFC 3040 [Active*]
- IETF RFC 3066 [Superseded*]
- IETF RFC 3075 [Superseded*]
- IETF RFC 3143 [Active*]
- IETF RFC 3150 [Active*]
- IETF RFC 3155 [Active*]
- IETF RFC 3157 [Active*]
- IETF RFC 3205 [Superseded*]
- IETF RFC 3234 [Active*]
- IETF RFC 3253 [Active*]
- IETF RFC 3261 [Active*]
- IETF RFC 3265 [Superseded*]
- IETF RFC 3275 [Active*]
- IETF RFC 3282 [Active*]
- IETF RFC 3297 [Active*]
- IETF RFC 3305 [Active*]
- IETF RFC 3367 [Active*]
- IETF RFC 3450 [Superseded*]
- IETF RFC 3451 [Superseded*]
- IETF RFC 3466 [Superseded*]
- IETF RFC 3489 [Superseded*]
- IETF RFC 3546 [Superseded*]
- IETF RFC 3552 [Active*]
- IETF RFC 3568 [Active*]
- IETF RFC 3617 [Active*]
- IETF RFC 3648 [Active*]
- IETF RFC 3696 [Active*]
- IETF RFC 3739 [Active*]
- IETF RFC 3744 [Active*]
- IETF RFC 3760 [Active*]
- IETF RFC 3819 [Active*]
- IETF RFC 3862 [Active*]
- IETF RFC 3864 [Active*]
- IETF RFC 3875 [Active*]
- IETF RFC 3903 [Active*]
- IETF RFC 3920 [Superseded*]
- IETF RFC 3926 [Superseded*]
- IETF RFC 3977 [Active*]
- IETF RFC 3983 [Active*]
- IETF RFC 3987 [Active*]
- IETF RFC 4145 [Active*]
- IETF RFC 4227 [Active*]
- IETF RFC 4325 [Superseded*]
- IETF RFC 4366 [Superseded*]
- IETF RFC 4559 [Active*]
- IETF RFC 4639 [Active*]
- IETF RFC 4647 [Active*]
- IETF RFC 4682 [Active*]
- IETF RFC 4743 [Active*]
- IETF RFC 4791 [Active*]
- IETF RFC 4825 [Active*]
- IETF RFC 4918 [Active*]
- IETF RFC 5019 [Superseded*]
- IETF RFC 5023 [Active*]
- IETF RFC 5198 [Active*]
- IETF RFC 5222 [Active*]
- IETF RFC 5280 [Active, Amended*]
- IETF RFC 5389 [Superseded*]
- IETF RFC 5545 [Active*]
- IETF RFC 5607 [Active*]
- IETF RFC 5646 [Active*]
- IETF RFC 5689 [Active*]
- IETF RFC 5775 [Active*]
- IETF RFC 5785 [Superseded*]
- IETF RFC 5789 [Active*]
- IETF RFC 5861 [Active*]
- IETF RFC 5878 [Active*]
- IETF RFC 5890 [Active*]
- IETF RFC 5927 [Active*]
- IETF RFC 5934 [Active*]
- IETF RFC 5987 [Superseded*]
- IETF RFC 5988 [Superseded*]
- IETF RFC 5989 [Active*]
- IETF RFC 5996 [Superseded*]
- IETF RFC 6042 [Active*]
- IETF RFC 6066 [Active*]
- IETF RFC 6120 [Active*]
- IETF RFC 6125 [Superseded*]
- IETF RFC 6202 [Active*]
- IETF RFC 6265 [Active*]
- IETF RFC 6266 [Active*]
- IETF RFC 6280 [Active*]
- IETF RFC 6350 [Active*]
- IETF RFC 6415 [Active*]
- IETF RFC 6454 [Active*]
- IETF RFC 6455 [Active*]
- IETF RFC 6585 [Active*]
- IETF RFC 6596 [Active*]
- IETF RFC 6648 [Active*]
- IETF RFC 6657 [Active*]
- IETF RFC 6690 [Active*]
- IETF RFC 6709 [Active*]
- IETF RFC 6726 [Active*]
- IETF RFC 6749 [Active*]
- IETF RFC 6750 [Active*]
- IETF RFC 6797 [Active*]
- IETF RFC 6838 [Active*]
- IETF RFC 6902 [Active*]
- IETF RFC 6920 [Active*]
- IETF RFC 6960 [Active*]
- IETF RFC 6973 [Active*]
- IETF RFC 7030 [Active*]
- IETF RFC 7230 [Superseded*]
- IETF RFC 7231 [Superseded*]
- IETF RFC 7232 [Superseded*]
- IETF RFC 7233 [Superseded*]
- IETF RFC 7234 [Superseded*]
- IETF RFC 7235 [Superseded*]
- IETF RFC 7252 [Active*]
- IETF RFC 7303 [Active*]
- IETF RFC 8075 [Active*]
- IETF RFC 8187 [Active*]
- SMPTE EG 39:2003 [Active, Stabilized]
- SMPTE ST 2032-1:2007 [Active, Stabilized]
- SMPTE ST 2032-2:2007 [Active, Stabilized]
- SMPTE ST 343:2002 [Active, Stabilized]
- SMPTE ST 364:2008 [Active, Stabilized]
- SMPTE ST 397:2003 [Active, Stabilized]
- SMPTE ST 430-14:2015 [Superseded]
- SMPTE ST 430-14:2021 [Active]