Visual RFC.
ALL RFCs / RFC 9113
Read the RFC ↗
RFC 9113 / MECHANISM GUIDE

Frames and compressed fields

03

A nine-octet frame header identifies length, type, flags, and stream.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 4.1 ↗
RFC 9113 · § 4.1EXAMPLE
3 / 3
Frames and compressed fieldsA nine-octet frame header identifies length, type, flags, and stream.Frames and compressed fieldsLength5TypeDATAFlagsENDStream ID1HEADERS → HPACK field blockHello
03
Read DATA

Content follows as DATA under the HTTP message rules.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

HEADERS carries compressed fields using HPACK, with CONTINUATION when needed.

  • HEADERS carries compressed fields using HPACK, with CONTINUATION when needed.
  • A field block must remain contiguous in its frame sequence.
  • Pseudo-header fields precede regular fields and describe request/response control data.
DETAILS

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
All chapters in this RFC
  1. Connection preface
  2. Multiplexed streams
  3. Frames and compressed fields
  4. Receiver flow-control credit
  5. Reset and graceful shutdown
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗