Expand description
Ordered pairs of token names and opaque byte values, without interpretation or section state. Protocol drivers decide which value bytes each protocol can carry: HTTP/2 and HTTP/3 extensions can negotiate binary values, so the semantic model does not restrict them.
Structs§
- Field
- One pair with a token name, retaining the original name spelling and value bytes.
- Fields
- Raw ordered pairs. Duplicate names, spelling, spacing, and opaque value
bytes are preserved. Interpretation belongs to an explicit header policy;
trailers are a separate
BodyFrame::Headersevent.