Request frame order
02Each request or response uses HEADERS, optional DATA, and optional trailing HEADERS.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 4.1 ↗
RFC 9114 · § 4.1EXAMPLE
3 / 3
03
Finish stream
Optional trailing HEADERS precede the end of the message.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
One request stream carries one exchange.
- One request stream carries one exchange.
- Pseudo-header fields carry method, scheme, authority, path, or status.
- A message with prohibited field ordering or inconsistent content length is malformed.
Examples are illustrative. Consult the linked RFC and its errata for implementation details.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy