Achieve RFC 9113 HTTP/2 Request Fields
Created November 6, 2026 · Updated November 6, 2026 · Achieve 3.1.0 · Qualified runtime: Node.js 24.22.2
Requirement levels: HTTP/2 field names, connection-specific fields, pseudo-header ordering, context, uniqueness, and required request pseudo-headers are governed by MUST and MUST NOT rules.
Achieve receives HTTP/2 requests through Node.js after nghttp2 has decoded HPACK and validated most field syntax. Achieve then validates authority consistency and request-target syntax visible at the application boundary.
Applicable requirements
- MUST: Under RFC 9113 §8.2.1, HTTP/2 field names must be lowercase; an uppercase field name makes the message malformed.
- MUST NOT: Under §8.2.2, an endpoint must not generate connection-specific fields or
Transfer-Encoding. A received message containing prohibited connection-specific fields is malformed;TEis permitted only with the valuetrailers. - MUST: Under §8.3, pseudo-headers must precede regular fields, occur only in their defined context, and not be duplicated.
- MUST: Under §8.3.1, a request has exactly one
:method; non-CONNECT requests also have exactly one:schemeand one valid:path. HTTP(S) paths are nonempty, with*used for asterisk-form OPTIONS; classic CONNECT omits:schemeand:path.
Authority and request handoff
Where authority information is required, Achieve accepts :authority or equivalent host information. If both appear, their normalized values must agree. Host case, default ports, IPv6 forms, and safe percent encodings are normalized before comparison. For the routing handoff and HTTP/1.1 comparison, see Request Targets and Authority.
Malformed-request behavior
Node/nghttp2 rejects tested uppercase names, prohibited connection fields, invalid TE, reordered or duplicate pseudo-headers, and missing or empty required pseudo-headers with stream PROTOCOL_ERROR; a later valid stream remains usable. Achieve closes an accepted request stream with the same error code when malformed target syntax is visible only after Node's compatibility handoff.
Verification and limits
Raw HPACK/frame probes exercise positive controls and each listed failure family, inspecting RST_STREAM, connection continuity, and whether the application callback runs. The broad requirement to handle every detected malformed HTTP/2 request remains Unverified: a finite corpus establishes the covered families, not every possible malformed message.
Node.js, nghttp2, and HPACK own field-block parsing and most error selection; Achieve cannot replace a protocol error already emitted before request dispatch. See the frame and HPACK evidence.
