Achieve RFC 9113 HTTP/2 Connections
Created November 6, 2026 · Updated November 6, 2026 · Achieve 3.1.0 · Qualified runtime: Node.js 24.22.2
Requirement levels: Connection establishment includes mandatory preface, SETTINGS, and TLS/ALPN requirements.
Achieve exposes cleartext HTTP/2 through listen2(port) and secure HTTP/2 through listen2(options). Both use Node's HTTP/2 compatibility API so accepted requests enter the same routing layer as HTTP/1.1.
Applicable requirements
- MUST: A client sends the connection preface followed by a SETTINGS frame; the server's first frame is a non-ACK SETTINGS frame (RFC 9113 §3.4).
- MUST: A secure connection selects HTTP/2 with ALPN
h2and meets the TLS requirements. - MAY: A client with prior knowledge can send the HTTP/2 preface directly on a cleartext connection (§3.3).
Cleartext and secure listeners
The cleartext listener is an h2c prior-knowledge endpoint created with Node's createServer(); it does not implement an HTTP/1.1 Upgrade exchange. The secure listener uses createSecureServer() with the supplied key, certificate, port, and other Node TLS/HTTP2 options.
Preface and application handoff
Node/nghttp2 recognizes the client preface, exchanges SETTINGS, constructs streams, decodes fields, and only then calls Achieve. Raw-frame captures verify that the first server frame is non-ACK SETTINGS on the qualified runtime. Invalid frame or preface processing remains a runtime responsibility.
Lifecycle and limits
Achieve returns the Node server object so the application can observe or close its listener. Stream states, GOAWAY, flow control, and protocol errors remain Node/nghttp2 behavior and are documented in their focused pages. The assessment does not infer every exceptional connection-close behavior from successful sessions.
Verification
All four transports—HTTP, HTTPS, h2c, and secure HTTP/2—are exercised by the verifier suite. Raw h2c and secure qualification probes inspect prefaces, the first SETTINGS frame, ALPN, requests, and connection-level failures.
