RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content

The Hypertext Transfer Protocol (HTTP) is a stateless \%application- level protocol for distributed, collaborative, hypertext information systems. This…

Read RFC 7231 on the RFC Editor

Outgoing relationships (28 related RFCs)

Updates, Informative reference — RFC 2817: Upgrading to TLS Within HTTP/1.1
Obsoletes, Informative reference — RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 3986: Uniform Resource Identifier (URI): Generic Syntax
Normative reference — RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching
Normative reference — RFC 7235: Hypertext Transfer Protocol (HTTP/1.1): Authentication
Normative reference — RFC 6365: Terminology Used in Internationalization in the IETF
Normative reference — RFC 7232: Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests
Informative reference — RFC 5226: Guidelines for Writing an IANA Considerations Section in RFCs
Informative reference — RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2
Informative reference — RFC 5905: Network Time Protocol Version 4: Protocol and Algorithms Specification
Informative reference — RFC 5322: Internet Message Format
Informative reference — RFC 6838: Media Type Specifications and Registration Procedures
Informative reference — RFC 6265: HTTP State Management Mechanism
Informative reference — RFC 1945: Hypertext Transfer Protocol -- HTTP/1.0
Informative reference — RFC 2068: Hypertext Transfer Protocol -- HTTP/1.1
Informative reference — RFC 2049: Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples
Informative reference — RFC 5988: Web Linking
Informative reference — RFC 2978: IANA Charset Registration Procedures
Informative reference — RFC 5789: PATCH Method for HTTP
Informative reference — RFC 5987: Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters
Informative reference — RFC 2295: Transparent Content Negotiation in HTTP
Informative reference — RFC 850: Standard for interchange of USENET messages
Informative reference — RFC 2388: Returning Values from Forms: multipart/form-data
Informative reference — RFC 2557: MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)
Informative reference — RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)
Informative reference — RFC 2774: An HTTP Extension Framework
Informative reference — RFC 7238: The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)

Incoming relationships (54 related RFCs)

Showing 50 of 54 related RFCs.

Obsoleted by — RFC 9110: HTTP Semantics
Normatively referenced by — RFC 7235: Hypertext Transfer Protocol (HTTP/1.1): Authentication
Normatively referenced by — RFC 7540: Hypertext Transfer Protocol Version 2 (HTTP/2)
Normatively referenced by — RFC 7481: Security Services for the Registration Data Access Protocol (RDAP)
Normatively referenced by — RFC 7616: HTTP Digest Access Authentication
Normatively referenced by — RFC 7480: HTTP Usage in the Registration Data Access Protocol (RDAP)
Normatively referenced by — RFC 7662: OAuth 2.0 Token Introspection
Normatively referenced by — RFC 9460: Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)
Normatively referenced by — RFC 7807: Problem Details for HTTP APIs
Normatively referenced by — RFC 7482: Registration Data Access Protocol (RDAP) Query Format
Normatively referenced by — RFC 8835: Transports for WebRTC
Normatively referenced by — RFC 8995: Bootstrapping Remote Secure Key Infrastructure (BRSKI)
Normatively referenced by — RFC 7486: HTTP Origin-Bound Authentication (HOBA)
Normatively referenced by — RFC 7644: System for Cross-domain Identity Management: Protocol
Normatively referenced by — RFC 7643: System for Cross-domain Identity Management: Core Schema
Normatively referenced by — RFC 8075: Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol (CoAP)
Normatively referenced by — RFC 7240: Prefer Header for HTTP
Normatively referenced by — RFC 7472: Internet Printing Protocol (IPP) over HTTPS Transport Binding and the 'ipps' URI Scheme
Normatively referenced by — RFC 7538: The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)
Normatively referenced by — RFC 7711: PKIX over Secure HTTP (POSH)
Normatively referenced by — RFC 7808: Time Zone Data Distribution Service
Normatively referenced by — RFC 8188: Encrypted Content-Encoding for HTTP
Normatively referenced by — RFC 8297: An HTTP Status Code for Indicating Hints
Normatively referenced by — RFC 8739: Support for Short-Term, Automatically Renewed (STAR) Certificates in the Automated Certificate Management Environment (ACME)
Normatively referenced by — RFC 8896: Application-Layer Traffic Optimization (ALTO) Cost Calendar
Normatively referenced by — RFC 7238: The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)
Normatively referenced by — RFC 7639: The ALPN HTTP Header Field
Normatively referenced by — RFC 8187: Indicating Character Encoding and Language for HTTP Header Field Parameters
Normatively referenced by — RFC 8295: EST (Enrollment over Secure Transport) Extensions
Normatively referenced by — RFC 8910: Captive-Portal Identification in DHCP and Router Advertisements (RAs)
Normatively referenced by — RFC 8935: Push-Based Security Event Token (SET) Delivery Using HTTP
Normatively referenced by — RFC 8936: Poll-Based Security Event Token (SET) Delivery Using HTTP
Normatively referenced by — RFC 7237: Initial Hypertext Transfer Protocol (HTTP) Method Registrations
Normatively referenced by — RFC 7545: Protocol to Access White-Space (PAWS) Databases
Normatively referenced by — RFC 7592: OAuth 2.0 Dynamic Client Registration Management Protocol
Normatively referenced by — RFC 7694: Hypertext Transfer Protocol (HTTP) Client-Initiated Content-Encoding
Normatively referenced by — RFC 7745: XML Schemas for Reverse DNS Management
Normatively referenced by — RFC 7846: Peer-to-Peer Streaming Tracker Protocol (PPSTP)
Normatively referenced by — RFC 8072: YANG Patch Media Type
Normatively referenced by — RFC 8802: The Quality for Service (Q4S) Protocol
Normatively referenced by — RFC 8804: Content Delivery Network Interconnection (CDNI) Request Routing Extensions
Normatively referenced by — RFC 8942: HTTP Client Hints
Normatively referenced by — RFC 8977: Registration Data Access Protocol (RDAP) Query Parameters for Result Sorting and Paging
Informatively referenced by — RFC 7617: The 'Basic' HTTP Authentication Scheme
Informatively referenced by — RFC 8941: Structured Field Values for HTTP
Informatively referenced by — RFC 8489: Session Traversal Utilities for NAT (STUN)
Informatively referenced by — RFC 8895: Application-Layer Traffic Optimization (ALTO) Incremental Updates Using Server-Sent Events (SSE)
Informatively referenced by — RFC 9040: TCP Control Block Interdependence
Informatively referenced by — RFC 8088: How to Write an RTP Payload Format
Informatively referenced by — RFC 7302: Entertainment Identifier Registry (EIDR) URN Namespace Definition