RFC 7230: Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing

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

Read RFC 7230 on the RFC Editor

Outgoing relationships (14 related RFCs)

Updates — RFC 2818: HTTP Over TLS
Updates — RFC 2817: Upgrading to TLS Within HTTP/1.1
Obsoletes, Informative reference — RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1
Obsoletes, Informative reference — RFC 2145: Use and Interpretation of HTTP Version Numbers
Normative reference — RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching
Normative reference — RFC 1951: DEFLATE Compressed Data Format Specification version 1.3
Normative reference — RFC 1950: ZLIB Compressed Data Format Specification version 3.3
Normative reference — RFC 1952: GZIP file format specification version 4.3
Informative reference — RFC 5226: Guidelines for Writing an IANA Considerations Section in RFCs
Informative reference — RFC 2045: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
Informative reference — RFC 2047: MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text
Informative reference — RFC 3864: Registration Procedures for Message Header Fields
Informative reference — RFC 2068: Hypertext Transfer Protocol -- HTTP/1.1
Informative reference — RFC 4559: SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft Windows

Incoming relationships (75 related RFCs)

Showing 50 of 75 related RFCs.

Updated by — RFC 8615: Well-Known Uniform Resource Identifiers (URIs)
Obsoleted by — RFC 9110: HTTP Semantics
Obsoleted by — RFC 9112: HTTP/1.1
Normatively referenced by — RFC 8341: Network Configuration Access Control Model
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 7616: HTTP Digest Access Authentication
Normatively referenced by — RFC 7480: HTTP Usage in the Registration Data Access Protocol (RDAP)
Normatively referenced by — RFC 7469: Public Key Pinning Extension for HTTP
Normatively referenced by — RFC 8226: Secure Telephone Identity Credentials: Certificates
Normatively referenced by — RFC 8941: Structured Field Values for HTTP
Normatively referenced by — RFC 7838: HTTP Alternative Services
Normatively referenced by — RFC 7239: Forwarded HTTP Extension
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 7541: HPACK: Header Compression for HTTP/2
Normatively referenced by — RFC 7828: The edns-tcp-keepalive EDNS0 Option
Normatively referenced by — RFC 8995: Bootstrapping Remote Secure Key Infrastructure (BRSKI)
Normatively referenced by — RFC 9176: Constrained RESTful Environments (CoRE) Resource Directory
Normatively referenced by — RFC 7644: System for Cross-domain Identity Management: Protocol
Normatively referenced by — RFC 7975: Request Routing Redirection Interface for Content Delivery Network (CDN) Interconnection
Normatively referenced by — RFC 8252: OAuth 2.0 for Native Apps
Normatively referenced by — RFC 7615: HTTP Authentication-Info and Proxy-Authentication-Info Response Header Fields
Normatively referenced by — RFC 8075: Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol (CoAP)
Normatively referenced by — RFC 8738: Automated Certificate Management Environment (ACME) IP Identifier Validation Extension
Normatively referenced by — RFC 8768: Constrained Application Protocol (CoAP) Hop-Limit Option
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 8164: Opportunistic Security for HTTP/2
Normatively referenced by — RFC 8188: Encrypted Content-Encoding for HTTP
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 8010: Internet Printing Protocol/1.1: Encoding and Transport
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 8894: Simple Certificate Enrolment Protocol
Normatively referenced by — RFC 8935: Push-Based Security Event Token (SET) Delivery Using HTTP
Normatively referenced by — RFC 7694: Hypertext Transfer Protocol (HTTP) Client-Initiated Content-Encoding
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 8292: Voluntary Application Server Identification (VAPID) for Web Push
Normatively referenced by — RFC 8673: HTTP Random Access and Live Content
Normatively referenced by — RFC 8740: Using TLS 1.3 with HTTP/2
Normatively referenced by — RFC 8802: The Quality for Service (Q4S) Protocol
Normatively referenced by — RFC 8898: Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)
Normatively referenced by — RFC 8977: Registration Data Access Protocol (RDAP) Query Parameters for Result Sorting and Paging
Normatively referenced by — RFC 9246: URI Signing for Content Delivery Network Interconnection (CDNI)
Informatively referenced by — RFC 8866: SDP: Session Description Protocol