RFC 9218: Extensible Prioritization Scheme for HTTP
In plain English — editorial summary, not part of the RFC
This document describes a scheme that allows an HTTP client to communicate its preferences for how the upstream server prioritizes responses to its requests, and also allows a server to hint to a downstream intermediary how its responses should be prioritized when they are forwarded. This document defines the Priority header field for communicating the initial priority in an HTTP version-independent manner, as well as HTTP/2 and HTTP/3 frames for reprioritizing responses. These share a common format structure that is designed to provide future extensibility.
Document record
- Document ID
- RFC9218
- Published
- June 2022
- Authors
- K. Oku; L. Pardue
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9220Bootstrapping WebSockets with HTTP/3Current
June 2022
- RFC 9221An Unreliable Datagram Extension to QUICCurrent
March 2022
- RFC 9213Targeted HTTP Cache ControlCurrent
June 2022
- RFC 9211The Cache-Status HTTP Response Header FieldCurrent
June 2022
- RFC 9209The Proxy-Status HTTP Response Header FieldCurrent
June 2022
- RFC 9205Building Protocols with HTTPCurrent
June 2022
- RFC 9204QPACK: Field Compression for HTTP/3Current
June 2022
- RFC 9235TCP Authentication Option (TCP-AO) Test VectorsCurrent
May 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?