RFC 9113: HTTP/2
In plain English — editorial summary, not part of the RFC
This specification describes an optimized expression of the semantics of the Hypertext Transfer Protocol (HTTP), referred to as HTTP version 2 (HTTP/2). HTTP/2 enables a more efficient use of network resources and a reduced latency by introducing field compression and allowing multiple concurrent exchanges on the same connection. This document obsoletes RFCs 7540 and 8740.
Document record
- Document ID
- RFC9113
- Published
- June 2022
- Authors
- M. Thomson; C. Benfield
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 78
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 7540 (2015)
- RFC 8740 (2020)
- RFC 9113 (2022)
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8291Message Encryption for Web PushCurrent
November 2017
- RFC 1945Hypertext Transfer Protocol -- HTTP/1.0Current
May 1996
- RFC 9112HTTP/1.1Updated
June 2022
- RFC 9114HTTP/3Current
June 2022
- RFC 9111HTTP CachingCurrent
June 2022
- RFC 9110HTTP SemanticsCurrent
June 2022
- RFC 9211The Cache-Status HTTP Response Header FieldCurrent
June 2022
- RFC 9264Linkset: Media Types and a Link Relation Type for Link SetsCurrent
July 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?