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 documentation index

Achieve RFC 9113 §5.4 HTTP/2 Connection and Stream Errors

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

Requirement levels: Multiple — applicable MUST and SHOULD requirements are identified below.

Achieve 3.1.0 uses Node.js HTTP/2 facilities to provide cleartext and secure HTTP/2 application servers. HTTP/2 multiplexes independent streams on one connection, so an error's scope is significant: a stream error ends one exchange, while a connection error affects every stream using that connection.

Applicable requirements

Connection errors

A connection error makes the HTTP/2 connection unusable. GOAWAY communicates the error code and the last stream that might have been processed, allowing a peer to determine which later requests can be retried. Closing the connection necessarily affects otherwise independent streams.

On the qualified Node.js 24.22.2 runtime, verified connection-level violations produce the error codes required by RFC 9113. These include an even-numbered client-initiated stream, invalid SETTINGS values, a client PUSH_PROMISE sent to the server, a connection-level WINDOW_UPDATE(0), and active flow-control-window overflow. The observed response is a connection GOAWAY with PROTOCOL_ERROR or FLOW_CONTROL_ERROR as applicable.

Stream errors

A stream error is confined to one stream. RST_STREAM terminates that stream while preserving unrelated work on the connection. This distinction prevents a malformed or failed request from unnecessarily disrupting other concurrent requests.

Node.js correctly applies stream-scoped PROTOCOL_ERROR to many malformed request conditions, including tested pseudo-header, field, request-target, trailer, and content-length errors. Achieve also closes an accepted request stream with PROTOCOL_ERROR when request-target syntax visible to the application layer is invalid.

Achieve and the Node.js protocol boundary

Achieve creates Node.js HTTP/2 servers and handles requests through Node's compatibility request and response interface. Node.js and its bundled nghttp2 library parse frames, decode HPACK field blocks, maintain stream state, enforce flow control, and select most protocol error frames before an accepted request reaches Achieve.

Achieve controls application routing and response behavior after that boundary. It does not implement a second HTTP/2 frame parser and cannot replace a GOAWAY or RST_STREAM already selected by Node.js or nghttp2. Raw-frame comparisons against standalone Node.js reproduce the relevant protocol results and identify the responsible layer.

Automated verification

Focused probes send exact HTTP/2 frames, maintain stream state deliberately, and decode returned GOAWAY and RST_STREAM payloads. Valid controls confirm that the connection and application callback work before the intentional violation. Contiguous and fragmented TCP delivery are compared where timing could otherwise produce a misleading result.

The final Node.js 24.22.2 Linux qualification reproduced the corrected connection-level results and the remaining known limitations without unexpected protocol failures. See Achieve HTTP conformance testing for the stable verifier entry point. Detailed evidence is retained in the HTTP/2 findings investigation and stream-state and flow-control review.

Known limitations

A zero-increment WINDOW_UPDATE on a valid open nonzero stream produces connection GOAWAY(PROTOCOL_ERROR) on the qualified runtime. The error code is correct, but RFC 9113 requires stream-scoped RST_STREAM(PROTOCOL_ERROR). The observed behavior is owned by the Node.js/nghttp2 protocol layer and unnecessarily terminates unrelated streams.

Opening a stream beyond the advertised concurrent-stream limit also produces a connection error instead of the specified stream treatment. This is likewise a Node.js/nghttp2 behavior rather than an Achieve application-routing decision.

Node.js 24.22.2 rejects a post-preface TLS 1.2 renegotiation attempt, but the verified secure HTTP/2 endpoint does not produce the GOAWAY(PROTOCOL_ERROR) required by RFC 9113 §9.2.1. Renegotiation remains disabled, but the TLS-to-HTTP/2 error signaling is an upstream Node.js/OpenSSL integration limitation.

The tested connection-error families normally produced GOAWAY before closure, but the broad §5.4.1 recommendation covers every detectable connection error and its “when possible” condition. The bounded evidence does not establish that universal claim. Similarly, many malformed-request families have correct stream treatment, but untested malformed conditions are not inferred to conform.