Achieve RFC 9113 HTTP/2 TLS Requirements
Created November 6, 2026 · Updated November 6, 2026 · Achieve 3.1.0 · Qualified runtime: Node.js 24.22.2
Requirement levels: Applicable MUST, SHOULD NOT, and MAY obligations are identified below.
Achieve creates secure HTTP/2 servers through Node.js. Node, OpenSSL, and nghttp2 perform TLS negotiation and HTTP/2 protocol signaling; Achieve supplies the server options and application callback.
Applicable requirements
- MUST: HTTP/2 over TLS uses TLS 1.2 or later and disables TLS compression (RFC 9113 §9.2).
- MUST: The TLS implementation supports ALPN
h2, and a server selectsh2before using HTTP/2 (§9.2.1). - MUST: TLS 1.2 deployments disable renegotiation and support
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256with P-256 (§9.2.2). - MUST: A post-preface TLS 1.2 renegotiation attempt is an HTTP/2 connection
PROTOCOL_ERROR, subject to the narrow pre-preface client-certificate exception. - SHOULD NOT / MAY: A TLS 1.2 endpoint should not negotiate a prohibited cipher; it may instead use
INADEQUATE_SECURITY.
Verified negotiation
Secure tests negotiate ALPN h2, TLS 1.2 or later, and no TLS compression. A constrained TLS 1.2 control successfully negotiated the mandatory AES-GCM cipher with P-256. Node.js 24.22.2 rejects client-initiated post-preface renegotiation.
Known limitations
After rejecting that renegotiation, the qualified runtime does not emit the required HTTP/2 PROTOCOL_ERROR; the connection ceases to be usable without the specified GOAWAY signal. This is Nonconformant at the Node/OpenSSL/nghttp2 boundary.
An explicitly configured TLS 1.2 server can negotiate a cipher from RFC 9113's prohibited list when OpenSSL security policy is deliberately lowered. The optional INADEQUATE_SECURITY response is not implemented. Default cipher selection was not implicated by that probe.
Configuration boundary
listen2(options) requires key and certificate values for secure operation and passes the options to Node's secure HTTP/2 server. Operator-supplied TLS policy can therefore affect the endpoint; the qualified results describe the tested Node.js 24.22.2 configuration, not every possible options object.
Verification
Windows and Linux qualification recorded TLS, OpenSSL, nghttp2, ALPN, cipher, curve, renegotiation, connection-closure, and control-PING observations. See the TLS investigation and Node 24 decision.
