Achieve RFC 9113 HTTP/2 Flow Control
Created November 6, 2026 · Updated November 6, 2026 · Achieve 3.1.0 · Qualified runtime: Node.js 24.22.2
Requirement levels: HTTP/2 flow control includes mandatory MUST and MUST NOT rules at both connection and stream scope.
Achieve relies on Node.js and its nghttp2 library for HTTP/2 flow control. Separate connection and stream windows bound DATA transmission without blocking control frames or other streams unnecessarily.
Applicable requirements
- MUST: Under RFC 9113 §5.2, flow control applies only to DATA frames and counts the entire DATA payload, including padding.
- MUST NOT: Under §6.9, a sender must not send a flow-controlled frame whose payload exceeds the available connection or stream window.
- MUST: A receiver detecting window exceedance must use
FLOW_CONTROL_ERRORat the applicable connection or stream scope. - MUST: A zero increment in
WINDOW_UPDATEisPROTOCOL_ERROR, at connection scope for stream 0 and stream scope for a nonzero stream. - MUST: §6.9.2 requires a change to
SETTINGS_INITIAL_WINDOW_SIZEto adjust every active stream window and handle overflow with the specified error.
Qualified runtime behavior
Bounded raw-frame tests show that Node/nghttp2 limits outbound DATA to both advertised windows, resumes only after corresponding credit, counts padding, rejects window overflow, and applies active initial-window changes. Connection-level WINDOW_UPDATE(0) produces GOAWAY(PROTOCOL_ERROR) as required.
Responsibility boundary
Node.js and nghttp2 parse WINDOW_UPDATE and SETTINGS, maintain windows, schedule DATA, and select protocol error frames before request content reaches Achieve. Achieve consumes the Node request stream and does not implement a parallel frame or flow-control layer. These runtime results are part of the released endpoint while their upstream ownership remains explicit.
Known limitations
A zero-increment WINDOW_UPDATE on a valid open nonzero stream produces connection GOAWAY(PROTOCOL_ERROR) on Node.js 24.22.2. The error code is correct, but §6.9 requires stream RST_STREAM(PROTOCOL_ERROR); unrelated streams are therefore terminated.
Stream-scope flow-control-window exceedance has been verified. The connection-scope receiver obligation remains Unverified: a peer can violate the protocol on the wire, but the available Node/nghttp2 interface automatically replenished connection credit, so the bounded probes did not establish a deterministic exceedance without altering internal state.
Verification
Focused raw-frame probes use controlled stream state, exact DATA lengths, padding, WINDOW_UPDATE, and SETTINGS frames, with contiguous and fragmented delivery. Valid controls confirm application and connection health. See the flow-control evidence review and final Unverified investigation.
