RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1

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…

Read RFC 2616 on the RFC Editor

Outgoing relationships (37 related RFCs)

Obsoletes, Informative reference — RFC 2068: Hypertext Transfer Protocol -- HTTP/1.1
Informative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Informative reference — RFC 2045: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
Informative reference — RFC 2026: The Internet Standards Process -- Revision 3
Informative reference — RFC 822: STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
Informative reference — RFC 2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
Informative reference — RFC 2047: MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text
Informative reference — RFC 1738: Uniform Resource Locators (URL)
Informative reference — RFC 2396: Uniform Resource Identifiers (URI): Generic Syntax
Informative reference — RFC 1305: Network Time Protocol (Version 3) Specification, Implementation and Analysis
Informative reference — RFC 2279: UTF-8, a transformation format of ISO 10646
Informative reference — RFC 2617: HTTP Authentication: Basic and Digest Access Authentication
Informative reference — RFC 1945: Hypertext Transfer Protocol -- HTTP/1.0
Informative reference — RFC 1766: Tags for the Identification of Languages
Informative reference — RFC 2049: Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples
Informative reference — RFC 2183: Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field
Informative reference — RFC 1951: DEFLATE Compressed Data Format Specification version 1.3
Informative reference — RFC 1866: Hypertext Markup Language - 2.0
Informative reference — RFC 1737: Functional Requirements for Uniform Resource Names
Informative reference — RFC 977: Network News Transfer Protocol
Informative reference — RFC 1950: ZLIB Compressed Data Format Specification version 3.3
Informative reference — RFC 1952: GZIP file format specification version 4.3
Informative reference — RFC 1036: Standard for interchange of USENET messages
Informative reference — RFC 1436: The Internet Gopher Protocol (a distributed document search and retrieval protocol)
Informative reference — RFC 1590: Media Type Registration Procedure
Informative reference — RFC 1808: Relative Uniform Resource Locators
Informative reference — RFC 1900: Renumbering Needs Work
Informative reference — RFC 1630: Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web
Informative reference — RFC 1806: Communicating Presentation Information in Internet Messages: The Content-Disposition Header
Informative reference — RFC 2069: An Extension to HTTP : Digest Access Authentication
Informative reference — RFC 850: Standard for interchange of USENET messages
Informative reference — RFC 2076: Common Internet Message Headers
Informative reference — RFC 1864: The Content-MD5 Header Field
Informative reference — RFC 1867: Form-based File Upload in HTML
Informative reference — RFC 2145: Use and Interpretation of HTTP Version Numbers
Informative reference — RFC 2324: Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)
Informative reference — RFC 2110: MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)

Incoming relationships (170 related RFCs)

Showing 50 of 170 related RFCs.

Updated by, Informatively referenced by — RFC 2817: Upgrading to TLS Within HTTP/1.1
Updated by, Informatively referenced by — RFC 5785: Defining Well-Known Uniform Resource Identifiers (URIs)
Updated by, Normatively referenced by — RFC 6585: Additional HTTP Status Codes
Updated by, Normatively referenced by — RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)
Obsoleted by, Informatively referenced by — RFC 7230: Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
Obsoleted by, Informatively referenced by — RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
Obsoleted by, Informatively referenced by — RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching
Obsoleted by, Informatively referenced by — RFC 7235: Hypertext Transfer Protocol (HTTP/1.1): Authentication
Obsoleted by, Informatively referenced by — RFC 7232: Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests
Obsoleted by, Informatively referenced by — RFC 7233: Hypertext Transfer Protocol (HTTP/1.1): Range Requests
Normatively referenced by — RFC 3261: SIP: Session Initiation Protocol
Normatively referenced by — RFC 6066: Transport Layer Security (TLS) Extensions: Extension Definitions
Normatively referenced by — RFC 3265: Session Initiation Protocol (SIP)-Specific Event Notification
Normatively referenced by — RFC 6749: The OAuth 2.0 Authorization Framework
Normatively referenced by — RFC 5996: Internet Key Exchange Protocol Version 2 (IKEv2)
Normatively referenced by — RFC 4366: Transport Layer Security (TLS) Extensions
Normatively referenced by — RFC 4918: HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)
Normatively referenced by — RFC 6454: The Web Origin Concept
Normatively referenced by — RFC 6750: The OAuth 2.0 Authorization Framework: Bearer Token Usage
Normatively referenced by — RFC 5988: Web Linking
Normatively referenced by — RFC 4791: Calendaring Extensions to WebDAV (CalDAV)
Normatively referenced by — RFC 7030: Enrollment over Secure Transport
Normatively referenced by — RFC 6690: Constrained RESTful Environments (CoRE) Link Format
Normatively referenced by — RFC 4825: The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)
Normatively referenced by — RFC 5789: PATCH Method for HTTP
Normatively referenced by — RFC 5985: HTTP-Enabled Location Delivery (HELD)
Normatively referenced by — RFC 5987: Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters
Normatively referenced by — RFC 3546: Transport Layer Security (TLS) Extensions
Normatively referenced by — RFC 6797: HTTP Strict Transport Security (HSTS)
Normatively referenced by — RFC 5055: Server-Based Certificate Validation Protocol (SCVP)
Normatively referenced by — RFC 6920: Naming Things with Hashes
Normatively referenced by — RFC 6928: Increasing TCP's Initial Window
Normatively referenced by — RFC 5023: The Atom Publishing Protocol
Normatively referenced by — RFC 5986: Discovering the Local Location Information Server (LIS)
Normatively referenced by — RFC 4743: Using NETCONF over the Simple Object Access Protocol (SOAP)
Normatively referenced by — RFC 5019: The Lightweight Online Certificate Status Protocol (OCSP) Profile for High-Volume Environments
Normatively referenced by — RFC 6442: Location Conveyance for the Session Initiation Protocol
Normatively referenced by — RFC 6546: Transport of Real-time Inter-network Defense (RID) Messages over HTTP/TLS
Normatively referenced by — RFC 5849: The OAuth 1.0 Protocol
Normatively referenced by — RFC 5861: HTTP Cache-Control Extensions for Stale Content
Normatively referenced by — RFC 5878: Transport Layer Security (TLS) Authorization Extensions
Normatively referenced by — RFC 6712: Internet X.509 Public Key Infrastructure -- HTTP Transfer for the Certificate Management Protocol (CMP)
Normatively referenced by — RFC 3466: A Model for Content Internetworking (CDI)
Normatively referenced by — RFC 3696: Application Techniques for Checking and Transformation of Names
Normatively referenced by — RFC 6080: A Framework for Session Initiation Protocol User Agent Profile Delivery
Normatively referenced by — RFC 6352: CardDAV: vCard Extensions to Web Distributed Authoring and Versioning (WebDAV)
Normatively referenced by — RFC 6726: FLUTE - File Delivery over Unidirectional Transport
Normatively referenced by — RFC 3568: Known Content Network (CN) Request-Routing Mechanisms
Normatively referenced by — RFC 3648: Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol
Normatively referenced by — RFC 4236: HTTP Adaptation with Open Pluggable Edge Services (OPES)