RFC 9110: HTTP Semantics

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

Read RFC 9110 on the RFC Editor

Outgoing relationships (10 related RFCs)

Updates — RFC 3864: Registration Procedures for Message Header Fields
Obsoletes — RFC 2818: HTTP Over TLS
Obsoletes — RFC 7230: Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
Obsoletes — RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
Obsoletes — RFC 7235: Hypertext Transfer Protocol (HTTP/1.1): Authentication
Obsoletes — RFC 7232: Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests
Obsoletes — RFC 7233: Hypertext Transfer Protocol (HTTP/1.1): Range Requests
Obsoletes — RFC 7615: HTTP Authentication-Info and Proxy-Authentication-Info Response Header Fields
Obsoletes — RFC 7538: The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)
Obsoletes — RFC 7694: Hypertext Transfer Protocol (HTTP) Client-Initiated Content-Encoding

Incoming relationships (59 related RFCs)

Showing 50 of 59 related RFCs.

Normatively referenced by — RFC 9114: HTTP/3
Normatively referenced by — RFC 9460: Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)
Normatively referenced by — RFC 9298: Proxying UDP in HTTP
Normatively referenced by — RFC 9230: Oblivious DNS over HTTPS
Normatively referenced by — RFC 9483: Lightweight Certificate Management Protocol (CMP) Profile
Normatively referenced by — RFC 9193: Sensor Measurement Lists (SenML) Fields for Indicating Data Value Content-Format
Normatively referenced by — RFC 9297: HTTP Datagrams and the Capsule Protocol
Normatively referenced by — RFC 9440: Client-Cert HTTP Header Field
Normatively referenced by — RFC 9530: Digest Fields
Normatively referenced by — RFC 9292: Binary Representation of HTTP Messages
Normatively referenced by — RFC 9421: HTTP Message Signatures
Normatively referenced by — RFC 9632: Finding and Using Geofeed Data
Normatively referenced by — RFC 9782: Entity Attestation Token (EAT) Media Types
Normatively referenced by — RFC 9264: Linkset: Media Types and a Link Relation Type for Link Sets
Normatively referenced by — RFC 9309: Robots Exclusion Protocol
Normatively referenced by — RFC 9560: Federated Authentication for the Registration Data Access Protocol (RDAP) Using OpenID Connect
Normatively referenced by — RFC 9811: Internet X.509 Public Key Infrastructure -- HTTP Transfer for the Certificate Management Protocol (CMP)
Normatively referenced by — RFC 9876: Updates to the IANA Registration Procedures for Constrained Application Protocol (CoAP) Content-Formats
Normatively referenced by — RFC 10003: Certificate Management over CMS (CMC): Transport Protocols
Normatively referenced by — RFC 9163: Expect-CT Extension for HTTP
Normatively referenced by — RFC 9237: An Authorization Information Format (AIF) for Authentication and Authorization for Constrained Environments (ACE)
Normatively referenced by — RFC 9248: Interoperability Profile for Relay User Equipment
Normatively referenced by — RFC 9399: Internet X.509 Public Key Infrastructure: Logotypes in X.509 Certificates
Normatively referenced by — RFC 9472: A YANG Data Model for Reporting Software Bills of Materials (SBOMs) and Vulnerability Information
Normatively referenced by — RFC 9512: YAML Media Type
Normatively referenced by — RFC 9532: HTTP Proxy-Status Parameter for Next-Hop Aliases
Normatively referenced by — RFC 9540: Discovery of Oblivious Services via Service Binding Records
Normatively referenced by — RFC 9578: Privacy Pass Issuance Protocols
Normatively referenced by — RFC 9636: The Time Zone Information Format (TZif)
Normatively referenced by — RFC 9646: Conveying a Certificate Signing Request (CSR) in a Secure Zero-Touch Provisioning (SZTP) Bootstrapping Request
Normatively referenced by — RFC 9674: Same-Origin Policy for the RPKI Repository Delta Protocol (RRDP)
Normatively referenced by — RFC 9727: api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs
Normatively referenced by — RFC 9728: OAuth 2.0 Protected Resource Metadata
Normatively referenced by — RFC 9729: The Concealed HTTP Authentication Scheme
Normatively referenced by — RFC 9773: ACME Renewal Information (ARI) Extension
Normatively referenced by — RFC 9842: Compression Dictionary Transport
Normatively referenced by — RFC 9875: HTTP Cache Groups
Normatively referenced by — RFC 9910: Registration Data Access Protocol (RDAP) Regional Internet Registry (RIR) Search
Normatively referenced by — RFC 9919: The Lightweight Online Certificate Status Protocol (OCSP) Profile for High-Volume Environments
Normatively referenced by — RFC 9931: Security Considerations for Optimistic Protocol Transitions in HTTP/1.1
Normatively referenced by — RFC 9977: Publishing End-Site Prefix Lengths
Normatively referenced by — RFC 9995: CBOR Object Signing and Encryption (COSE) Hash Envelope
Normatively referenced by — RFC 10006: Automatic SIP Trunking and Peering
Informatively referenced by — RFC 9645: YANG Groupings for TLS Clients and TLS Servers
Informatively referenced by — RFC 9525: Service Identity in TLS
Informatively referenced by — RFC 9200: Authentication and Authorization for Constrained Environments Using the OAuth 2.0 Framework (ACE-OAuth)
Informatively referenced by — RFC 9203: The Object Security for Constrained RESTful Environments (OSCORE) Profile of the Authentication and Authorization for Constrained Environments (ACE) Framework
Informatively referenced by — RFC 9277: On Stable Storage for Items in Concise Binary Object Representation (CBOR)
Informatively referenced by — RFC 9449: OAuth 2.0 Demonstrating Proof of Possession (DPoP)
Informatively referenced by — RFC 9623: Implementing Interfaces to Transport Services