Achieve RFC 9113 HTTP/2 Stream States
Created November 6, 2026 · Updated November 6, 2026 · Achieve 3.1.0 · Qualified runtime: Node.js 24.22.2
Requirement levels: RFC 9113 defines mandatory stream-state transitions, identifier rules, concurrency limits, and state-specific error scope.
Achieve receives HTTP/2 requests only after Node.js and nghttp2 have opened and validated their streams. The stream state machine decides which frames are meaningful, when one direction has ended, and whether an error belongs to one stream or the whole connection.
Applicable requirements
- MUST: Implementations must apply the state-dependent frame rules and error handling in RFC 9113 §5.1.
- MUST: Client-initiated streams use odd identifiers, newly opened identifiers increase monotonically, and a reused lower identifier is treated as closed (§5.1.1).
- MUST: A peer must not create more active streams than the receiver's advertised concurrent-stream limit; a new excess stream requires a stream error (§5.1.2).
- MUST: Stream errors terminate the affected stream with
RST_STREAM, without unnecessarily terminating other streams (§5.4.2).
Lifecycle at the application boundary
Streams progress through idle, open, half-closed, and closed states as HEADERS, DATA, END_STREAM, RST_STREAM, and connection events are processed. Achieve works through Node's request and response stream APIs; it does not parse frame headers or maintain a competing protocol state machine.
On Node.js 24.22.2, bounded probes confirm correct client-stream parity, monotonically increasing identifiers, handling of lower closed identifiers, and continued service of already accepted streams when the advertised concurrency limit is reduced.
Known error-scope limitations
Two demonstrated nghttp2 behaviors remain outside the RFC-required scope. Opening a stream beyond the advertised concurrency limit terminates the connection with GOAWAY(PROTOCOL_ERROR) instead of rejecting only that stream. A zero-increment WINDOW_UPDATE on a valid open stream likewise produces connection GOAWAY rather than RST_STREAM(PROTOCOL_ERROR).
These cases make the composite state-machine obligation nonconformant on the qualified endpoint. Achieve cannot convert them after the fact because the runtime rejects the frame before application dispatch. Detailed code and scope analysis is in HTTP/2 Stream Errors and Connection Errors; window behavior is in HTTP/2 Flow Control.
Verification and open scope
Raw-frame tests deliberately hold streams open, control END_STREAM, vary identifiers, exceed advertised concurrency, and send state-sensitive frames with contiguous and fragmented TCP delivery. Valid requests on other streams distinguish stream survival from connection termination.
The broad recommendation to send GOAWAY whenever a connection error can be detected remains Unverified beyond the directly exercised error families; bounded tests are not generalized to every possible state violation.
