Achieve — High Level Logic Project. Creating a new meta design pattern.

Friendly in development. Fast in production. Just build your apps. Let Achieve do the rest.

← Back to technical specifications

Achieve RFC 9113 HTTP/2 Frames

Created November 6, 2026 · Updated November 6, 2026 · Achieve 3.1.0 · Qualified runtime: Node.js 24.22.2

Requirement levels: HTTP/2 framing includes mandatory format, size, sequencing, acknowledgement, and error rules.

Achieve delegates the HTTP/2 binary framing layer to Node.js and nghttp2. Achieve sees decoded requests and response streams, while the runtime reads and writes DATA, HEADERS, SETTINGS, PING, WINDOW_UPDATE, RST_STREAM, and GOAWAY frames.

Applicable requirements

Qualified frame behavior

The server begins with SETTINGS, acknowledges valid settings, emits empty SETTINGS ACK frames, and acknowledges PING data exactly. Unknown frame types are discarded without preventing a subsequent request. The reserved stream bit is ignored on input and unset on observed output.

Oversized DATA, malformed SETTINGS lengths, and type-specific size errors produced the required FRAME_SIZE_ERROR. Node.js 24.22.2 also supplies the required error codes for the tested invalid SETTINGS values and for a client-sent PUSH_PROMISE, correcting historical Node 22 findings.

Field-block sequencing

Captured server output keeps HEADERS and its CONTINUATION frames contiguous. Receiver probes show that interleaving another frame, changing streams mid-block, or sending an orphan CONTINUATION terminates the connection. Compression-specific behavior is documented in HTTP/2 Header Compression.

Responsibility boundary and limits

Frame parsing, serialization, ACKs, and protocol errors occur within Node/nghttp2 before Achieve application routing. Achieve selects application response content but cannot revise a frame error already emitted by the runtime. Known stream-versus-connection scope defects are documented in HTTP/2 Stream Errors and Connection Errors, not treated as generic framing success.

The broad recommendation to emit GOAWAY whenever a connection error can be detected remains Unverified outside the exercised families. The evidence is a substantial bounded corpus, not proof over every possible binary input.

Verification

Raw h2c probes construct frame headers and payloads directly, inspect returned frame types, flags, stream IDs, payloads, and error codes, and follow malformed cases with valid controls where the connection should survive. See the frame and HPACK probe record.