Achieve RFC 9113 HTTP/2 Header Compression
Created November 6, 2026 · Updated November 6, 2026 · Achieve 3.1.0 · Qualified runtime: Node.js 24.22.2
Requirement levels: RFC 9113 makes correct field-block sequencing and compression-error handling mandatory; HPACK encoding and state are defined by RFC 7541.
Achieve receives decoded HTTP/2 fields from Node.js. Node and nghttp2 apply HPACK, maintain the connection's compression context, and reject malformed compressed blocks before Achieve routing or servlet invocation.
Applicable requirements
- MUST: A fragmented field block is sent as HEADERS or PUSH_PROMISE followed by a contiguous sequence of CONTINUATION frames on the same stream (RFC 9113 §4.3).
- MUST: A failure to decompress a field block is a connection error of type
COMPRESSION_ERROR(§4.3). - MUST: Even when a field section is too large for application use, an implementation processes enough of its field block to maintain a consistent compression context unless it closes the connection (§10.5.1).
Connection-scoped compression state
HPACK reduces repeated field data with static and dynamic tables shared by field blocks on one connection. Dynamic-table updates therefore affect later streams, while a new connection begins with independent state. Achieve does not expose or duplicate that table.
Captured server output keeps fragmented response field blocks contiguous. Receiver tests reconstruct valid fragmented requests and reject interleaving, wrong-stream CONTINUATION, and orphan CONTINUATION sequences at connection scope.
Malformed compressed blocks
Invalid index zero, unterminated integer encoding, an excessive dynamic-table size update, a misplaced size update, and a fresh connection's reference to a nonexistent dynamic entry each produced GOAWAY(COMPRESSION_ERROR). These cases exercise distinct decoder failures without claiming that a finite corpus enumerates every invalid byte string.
Maintaining context after rejection
A dependent field block following an excessive field section decoded successfully using the earlier dynamic-table insertion. This establishes that the runtime processed enough of the rejected section to keep the connection context consistent for the exercised case. Resource limits and application rejection remain separate from compression correctness.
Responsibility and limits
HPACK encoding, decoding, table state, and compression errors belong to Node/nghttp2. Achieve validates the decoded request information it receives. A connection-level HPACK error cannot be replaced by application error handling because no safe request has reached Achieve.
Verification
Raw-frame probes provide exact HPACK octets, dynamic-table dependencies, fragmented field blocks, and fresh-connection controls, then inspect GOAWAY codes and connection usability. See the frame and HPACK probe record and final Unverified investigation.
