RFC 7540: Hypertext Transfer Protocol Version 2 (HTTP/2)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9113.
Current document in this lineage: 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 perception of latency by introducing header field compression and allowing multiple concurrent exchanges on the same connection. It also introduces unsolicited push of representations from servers to clients. This specification is an alternative to, but does not obsolete, the HTTP/1.1 message syntax. HTTP's existing semantics remain unchanged.
Document record
- Document ID
- RFC7540
- Published
- May 2015
- Authors
- M. Belshe; R. Peon; M. Thomson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 96
- 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) ✓
Referenced by
2 later RFCs formally update or obsolete part of this document.
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 7541HPACK: Header Compression for HTTP/2Current
May 2015
- RFC 7538The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)Obsoleted
April 2015
- RFC 7615HTTP Authentication-Info and Proxy-Authentication-Info Response Header FieldsObsoleted
September 2015
- RFC 7694Hypertext Transfer Protocol (HTTP) Client-Initiated Content-EncodingObsoleted
November 2015
- RFC 7838HTTP Alternative ServicesCurrent
April 2016
- RFC 7237Initial Hypertext Transfer Protocol (HTTP) Method RegistrationsCurrent
June 2014
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?