Achieve RFC 9113 HTTP/2 SETTINGS
Created November 6, 2026 · Updated November 6, 2026 · Achieve 3.1.0 · Qualified runtime: Node.js 24.22.2
Requirement levels: SETTINGS acknowledgement, payload, value-range, and application rules are mandatory.
Achieve delegates SETTINGS framing and state to Node.js/nghttp2. Settings take effect at the connection layer before or alongside application streams; Achieve does not parse SETTINGS frames.
Applicable requirements
- MUST: A recipient acknowledges applied settings (RFC 9113 §6.5).
- MUST: An ACK SETTINGS frame has an empty payload; otherwise the connection receives
FRAME_SIZE_ERROR. - MUST: Values outside a setting's defined range receive the error specified by §6.5.2.
- MUST: Changes to
SETTINGS_INITIAL_WINDOW_SIZEadjust active stream windows and handle overflow as specified. - MUST NOT: A server does not push after a client disables push.
Qualified behavior
Observed sessions exchange SETTINGS and empty acknowledgements. A nonempty ACK payload produces connection FRAME_SIZE_ERROR. Node.js 24.22.2 produces the specified errors for the tested invalid ENABLE_PUSH, MAX_FRAME_SIZE, and initial-window values; these correct historical Node 22 error-code findings.
A dynamic reduction in the advertised concurrent-stream limit allowed already open streams to complete, one of the alternatives RFC 9113 permits. Initial-window changes adjust active stream credit; tested overflow uses the required FLOW_CONTROL_ERROR.
Responsibility and configuration
Node/nghttp2 owns validation, acknowledgement, application timing, and flow-control effects. Achieve passes the secure or cleartext server options to Node and provides no separate SETTINGS API. Any Node-supported HTTP/2 settings supplied through server options remain subject to Node's validation and semantics.
Verification
Raw-frame probes inspect SETTINGS, ACK flags and payloads, invalid ranges, dynamic stream limits, initial-window changes, and subsequent connection health. See the frame probes and flow-control review.
