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.

Achieve RFC 9113 HTTP/2

Achieve: 3.1.0
Evaluated runtime: Node.js 24.22.2
Assessment baseline: November 5, 2026
Document status: Qualified release assessment

This register presents all 62 authoritative V3 requirements for RFC 9113. Requirement text is a traceable summary; the linked RFC Editor section supplies the controlling normative text and conditions.

ClassificationCount
Conformant49
Nonconformant6
Unverified3
Not applicable3
Optional not implemented1
Total62

Review the overall findings · Read the methodology · Inspect evidence sources

V3-9113-001 — RFC 9113 §3.4

Conformant Normative level: MUST

Requirement
The first server frame after the connection preface must be a non-ACK SETTINGS frame.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
server
Responsible layer
Node.js HTTP/2 session, stream, framing, and flow-control implementation
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
Successful h2c and h2 sessions in tests/http2_authority/verify.js require preface/SETTINGS exchange and acknowledgement; suite passed locally.
Assessment rationale
Successful standard Node HTTP/2 connections establish that the first server frame is acceptable as the required non-ACK SETTINGS frame on both transports.
Open question
None for the established scope.
V2 traceability
V2-NEW-049

V3-9113-002 — RFC 9113 §4.2

Conformant Normative level: MUST

Requirement
A recipient MUST treat frames larger than the advertised maximum as FRAME_SIZE_ERROR.
Conditions
Apply only under the conditions and exceptions stated in the cited section.
Applicable role
sender/recipient
Responsible layer
Node.js HTTP/2 session, stream, framing, and flow-control implementation
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
http2-frame-hpack-probes.md P08 sent a 16,385-byte DATA frame when the advertised/default maximum was 16,384; Node 22.15.0 returned GOAWAY FRAME_SIZE_ERROR.
Assessment rationale
P08 directly exercised a frame exceeding SETTINGS_MAX_FRAME_SIZE and observed the exact RFC 9113 section 4.2 error code and connection scope.
Open question
No material uncertainty for the exercised recipient obligation; behavior is qualified to the assessed Node.js 22.15.0 endpoint.
V2 traceability
V2-H202

V3-9113-003 — RFC 9113 §4.1

Conformant Normative level: MUST

Requirement
Recipients must ignore the reserved frame-header bit when receiving and leave it unset when sending.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
sender/recipient
Responsible layer
Node.js HTTP/2 session, stream, framing, and flow-control implementation
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
P01 in http2-frame-hpack-probes.md directly verifies receiver handling. Batch F observed the sender bit clear on the representative SETTINGS, SETTINGS ACK, HEADERS, RST_STREAM, and GOAWAY frames captured by that campaign.
Assessment rationale
The direct receiver probe and bounded sender captures establish the behavior for the tested Node/nghttp2 endpoint and observed frame families; they do not constitute an exhaustive capture of every frame type.
Open question
Additional sender frame families would require further capture if universal frame-type coverage were desired.
V2 traceability
V2-NEW-050

V3-9113-004 — RFC 9113 §4.1

Conformant Normative level: MUST

Requirement
Implementations must ignore unknown frame types.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
HTTP participant
Responsible layer
Node.js HTTP/2 session, stream, framing, and flow-control implementation
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
http2-frame-hpack-probes.md P02 sent unknown frame type 0xfe and then a valid request; the unknown frame was discarded and the request succeeded.
Assessment rationale
P02 directly exercised the section 4.1 recipient obligation to ignore and discard an unknown frame type while preserving connection usability.
Open question
No material uncertainty for the recipient obligation on the assessed Node.js 22.15.0 endpoint.
V2 traceability
V2-NEW-051

V3-9113-005 — RFC 9113 §4.3

Conformant Normative level: MUST

Requirement
Field blocks MUST be transmitted as a contiguous sequence of HEADERS or PUSH_PROMISE followed by CONTINUATION frames, without interleaving frames of another type or stream.
Conditions
The endpoint sends a field block spanning more than one frame.
Applicable role
HTTP/2 sender
Responsible layer
Node.js HTTP/2 and nghttp2 field-block serializer
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; Node/nghttp2 owns response field-block framing.
Test evidence
The final-unverified probe made Achieve send a 40,000-octet response field. Raw h2c capture showed HEADERS length 16,384 without END_HEADERS immediately followed on the same stream by one CONTINUATION length 8,679 with END_HEADERS; DATA followed only after the field block completed.
Assessment rationale
The exact multi-frame sender condition was exercised, and no frame of another type or stream was interleaved. Existing P04-P07 separately establish receiver behavior.
Open question
The capture is version-specific to Node.js 22.15.0/nghttp2 1.64.0; PUSH_PROMISE is not generated by this origin server, but the centralized serializer produced the required sequence for the applicable response field block.
V2 traceability
V2-X044

V3-9113-006 — RFC 9113 §4.3

Conformant Normative level: MUST

Requirement
A decoding failure in a field block is a connection error of type COMPRESSION_ERROR.
Conditions
HPACK decoding fails.
Applicable role
HTTP endpoint
Responsible layer
Node.js HTTP/2 and nghttp2 HPACK implementation
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
http2-frame-hpack-probes.md P25-P28 and P30 exercised invalid index zero, a truncated integer, oversized and misplaced table-size updates, and an unavailable dynamic index; each produced connection COMPRESSION_ERROR.
Assessment rationale
Representative, structurally distinct HPACK decoding failures all produced the exact mandatory connection error; conformance does not require enumerating every invalid octet string.
Open question
No material uncertainty for the decoding-failure obligation on the assessed Node.js 22.15.0 endpoint.
V2 traceability
V2-X045

V3-9113-007 — RFC 9113 §5.1

Nonconformant Normative level: MUST

Requirement
An endpoint MUST enforce the state-dependent permitted frame types and apply the specified stream or connection error for violations.
Conditions
Composite summary record covering the section 5.1 state-dependent frame and error obligations; individual rules remain separately traceable where the inventory contains them.
Applicable role
HTTP endpoint
Responsible layer
Node.js HTTP/2 session, stream, framing, and flow-control implementation
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing. The focused investigation shows the malformed frames are rejected by Node/nghttp2 before Achieve request dispatch; standalone Node reproduces the wire result.
Test evidence
Historical raw-frame investigations established the error families and removed fragmentation artifacts. Final Node.js 24.22.2 Windows and Linux qualification repeated the remaining stream WINDOW_UPDATE(0) and excess-concurrency counterexamples.
Assessment rationale
This record is intentionally retained as a composite summary for V2 traceability. Node.js 24.22.2 corrects the earlier tested connection-level error-code substitutions, but stream WINDOW_UPDATE(0) and excess-concurrency cases still have incorrect connection scope. One applicable counterexample establishes the composite MUST as Nonconformant for the qualified configuration.
Open question
Untested state transitions remain unverified independently of the demonstrated failures; consult the narrower records rather than treating this composite as exhaustive verification.
V2 traceability
V2-X046

V3-9113-008 — RFC 9113 §5.1.1

Conformant Normative level: MUST

Requirement
Newly established client-initiated streams use odd identifiers; invalid parity is a connection error.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
client
Responsible layer
Node.js 24.22.2/nghttp2 1.70.0 HTTP/2 session and framing implementation
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing. Node/nghttp2 owns the parity check before Achieve request dispatch.
Test evidence
http2-five-findings-investigation.md preserves the historical Node 22.15.0 GOAWAY(INTERNAL_ERROR) result. node24-adoption-decision.md and final Linux qualification run 42049611849 repeat a client HEADERS opening even stream 2 on Node 24.22.2 and observe connection GOAWAY(PROTOCOL_ERROR).
Assessment rationale
The released Achieve 3.1.0 / Node.js 24.22.2 endpoint uses the required connection error for the directly exercised invalid client-stream parity case. The prior Node 22 failure remains historical evidence and is attributed below Achieve application logic.
Open question
The evidence establishes the previously failing parity case on the qualified runtime; other stream-state obligations remain independently classified.
V2 traceability
V2-NEW-052

V3-9113-009 — RFC 9113 §5.1.1

Conformant Normative level: MUST

Requirement
New stream identifiers must increase monotonically; reuse or invalid ordering has defined error handling.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
HTTP participant
Responsible layer
Node.js HTTP/2 session, stream, framing, and flow-control implementation
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
http2-frame-hpack-probes.md P17; batch-e-evidence-review.md E02.
Assessment rationale
A lower new identifier receives connection PROTOCOL_ERROR; a repeated HEADERS block on the closed identifier is discarded rather than opening a second request, consistent with the closed-stream exceptions. Achieve initiates no push streams.
Open question
None for the supported origin-server scope.
V2 traceability
V2-NEW-053

V3-9113-010 — RFC 9113 §5.1.2

Conformant Normative level: MUST

Requirement
An endpoint must not exceed the peer's advertised maximum concurrent streams.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
HTTP endpoint
Responsible layer
Node.js HTTP/2 session, stream, framing, and flow-control implementation
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
Achieve never calls pushStream or initiates request streams; no repository test exercises server-initiated streams.
Assessment rationale
Achieve initiates no request streams and performs no server push, so it cannot exceed a peer limit for server-initiated streams.
Open question
None for the established scope.
V2 traceability
V2-NEW-054

V3-9113-011 — RFC 9113 §5.1.2

Conformant Normative level:

Requirement
An endpoint reducing its advertised maximum below the current number of open streams can close excess streams or allow them to complete.
Conditions
The endpoint reduces SETTINGS_MAX_CONCURRENT_STREAMS below the current number of open streams.
Applicable role
HTTP endpoint
Responsible layer
Node.js HTTP/2 session and dynamic SETTINGS handling
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers and delegates dynamic SETTINGS behavior to Node/nghttp2.
Test evidence
A focused Node.js 22.15.0 control held streams 1 and 3 open, reduced advertised SETTINGS_MAX_CONCURRENT_STREAMS from unlimited to 1, observed the client receive the new value, and then allowed both pre-existing streams to complete normally.
Assessment rationale
The exact dynamic-reduction condition was exercised and the endpoint selected one of the two behavior alternatives RFC 9113 permits: allowing excess existing streams to complete.
Open question
The probe used standalone Node because Achieve adds no protocol-layer handling here; application code does not ordinarily change the server's advertised limit.
V2 traceability
V2-X047A

V3-9113-012 — RFC 9113 §5.1.2

Nonconformant Normative level: MUST

Requirement
A receiver MUST treat a newly opened stream that exceeds its advertised maximum-concurrent-streams limit as the specified stream error.
Conditions
A peer opens a new stream beyond the advertised limit outside the permitted concurrency race.
Applicable role
HTTP endpoint
Responsible layer
Node.js 24.22.2/nghttp2 1.70.0 HTTP/2 stream-concurrency handling
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers and delegates the frame state machine to Node/nghttp2.
Test evidence
Batch E established the controlled stream lifetime and fragmentation result. Final Node.js 24.22.2 Windows and Linux qualification repeated the case with MAX_CONCURRENT_STREAMS=1 and stream 1 held open.
Assessment rationale
Opening stream 3 produces connection GOAWAY(PROTOCOL_ERROR) rather than the required stream PROTOCOL_ERROR or REFUSED_STREAM. Node 24 corrects the earlier error code but not the error scope.
Open question
The upstream stream-scope defect remains; repeat when the supported Node/nghttp2 baseline changes.
V2 traceability
V2-X047B

V3-9113-013 — RFC 9113 §5.2

Conformant Normative level:

Requirement
HTTP/2 flow control applies only to DATA frames and counts padding in the controlled octets.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
HTTP endpoint
Responsible layer
Node.js/nghttp2 flow-control implementation
Implementation evidence
achieve.js:1463-1512 delegates HTTP/2 framing and flow control to Node/nghttp2.
Test evidence
batch-e-evidence-review.md E05-E10.
Assessment rationale
HEADERS and SETTINGS acknowledgements remain transmissible at zero DATA credit; isolated DATA windows are enforced; a padded DATA payload exceeding the stream window by one produces FLOW_CONTROL_ERROR in contiguous and fragmented delivery.
Open question
None for the tested flow-control accounting scope.
V2 traceability
V2-NEW-055

V3-9113-014 — RFC 9113 §5.4.1

Unverified Normative level: SHOULD

Requirement
An endpoint detecting a connection error SHOULD send GOAWAY with the applicable error code before closing when possible.
Conditions
The endpoint can close immediately when sending GOAWAY is not possible.
Applicable role
HTTP endpoint
Responsible layer
Node.js HTTP/2 session, stream, framing, and flow-control implementation
Implementation evidence
achieve.js:1463-1512 delegates HTTP/2 connection-error framing to Node/nghttp2.
Test evidence
http2-frame-hpack-probes.md P05-P24 and batch-e-evidence-review.md E03 show GOAWAY before closure for all observed connection-error categories.
Assessment rationale
The representative corpus is strong evidence but does not establish the record's universal every-connection-error and when-possible conditions; no counterexample to the GOAWAY-before-close recommendation was found.
Open question
Either split the broad record into bounded error families or obtain authoritative version-specific coverage for the remaining conditions.
V2 traceability
V2-H207

V3-9113-015 — RFC 9113 §5.4.2

Nonconformant Normative level: MUST

Requirement
An endpoint detecting a stream error MUST send RST_STREAM with the applicable error code, subject to the closed-stream exceptions.
Conditions
Connection errors and already-closed streams have separate handling.
Applicable role
HTTP endpoint
Responsible layer
Node.js 24.22.2/nghttp2 1.70.0 stream-error handling
Implementation evidence
achieve.js:1463-1512 delegates HTTP/2 error framing to Node/nghttp2.
Test evidence
The five-findings investigation and Batch E removed the application-response race. Final Node.js 24.22.2 Windows and Linux qualification repeated open-stream WINDOW_UPDATE(0) and observed connection GOAWAY(PROTOCOL_ERROR).
Assessment rationale
Many malformed-message stream errors correctly receive RST_STREAM, but an open nonzero stream receiving WINDOW_UPDATE(0) gets a connection error instead of its required stream reset. This is the same underlying cause recorded by V3-9113-026.
Open question
Repeat the known counterexample when the supported Node/nghttp2 baseline changes.
V2 traceability
V2-H208

V3-9113-016 — RFC 9113 §6.5

Conformant Normative level: MUST

Requirement
A SETTINGS recipient must acknowledge applied settings.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
sender/recipient
Responsible layer
Node.js HTTP/2 session, stream, framing, and flow-control implementation
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
Successful h2c and h2 sessions in tests/http2_authority/verify.js require preface/SETTINGS exchange and acknowledgement; suite passed locally.
Assessment rationale
Successful sessions and requests require the SETTINGS exchange and acknowledgement to complete; observed on h2c and h2.
Open question
None for the established scope.
V2 traceability
V2-NEW-057

V3-9113-017 — RFC 9113 §6.5

Conformant Normative level: MUST

Requirement
A SETTINGS frame with ACK must have an empty payload; otherwise FRAME_SIZE_ERROR.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
HTTP participant
Responsible layer
Node.js HTTP/2 session, stream, framing, and flow-control implementation
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
http2-frame-hpack-probes.md P09 sent SETTINGS with ACK and a six-byte payload; Node 22.15.0 returned GOAWAY FRAME_SIZE_ERROR.
Assessment rationale
P09 directly exercised the exact section 6.5 ACK-payload condition and observed the mandatory error code and connection scope.
Open question
No material uncertainty for this exact obligation.
V2 traceability
V2-NEW-058

V3-9113-018 — RFC 9113 §6.5.2

Conformant Normative level: MUST NOT

Requirement
A server must not push when the client has disabled push; violation is a connection error.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
client
Responsible layer
Node.js HTTP/2 session, stream, framing, and flow-control implementation
Implementation evidence
No pushStream call exists in achieve.js; achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
Achieve never calls pushStream or initiates request streams; no repository test exercises server-initiated streams.
Assessment rationale
Achieve never invokes server push, so it does not push when the peer disables push.
Open question
None for the established scope.
V2 traceability
V2-NEW-072

V3-9113-019 — RFC 9113 §6.5.2

Conformant Normative level: MUST

Requirement
A recipient MUST treat a SETTINGS value outside its defined range as the specified connection error.
Conditions
Defined setting-specific range violated.
Applicable role
HTTP endpoint
Responsible layer
Node.js 24.22.2/nghttp2 1.70.0 HTTP/2 SETTINGS implementation
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing. Node/nghttp2 validates SETTINGS before Achieve request dispatch.
Test evidence
http2-five-findings-investigation.md preserves the historical Node 22.15.0 GOAWAY(INTERNAL_ERROR) results. node24-adoption-decision.md and final Linux qualification run 42049611849 send SETTINGS_ENABLE_PUSH=2 and SETTINGS_MAX_FRAME_SIZE=16383 on Node 24.22.2; both receive the required connection GOAWAY(PROTOCOL_ERROR).
Assessment rationale
The two defined out-of-range SETTINGS cases that previously demonstrated nonconformance now produce the specified connection error on the released Achieve 3.1.0 / Node.js 24.22.2 endpoint. The correction belongs to the runtime protocol layer, not Achieve application logic.
Open question
The bounded probes establish the formerly failing defined-range cases; they do not imply exhaustive coverage of every setting-specific range.
V2 traceability
V2-X048

V3-9113-020 — RFC 9113 §6.6

Conformant Normative level: MUST

Requirement
A server receiving PUSH_PROMISE MUST treat it as a connection error of type PROTOCOL_ERROR.
Conditions
Servers cannot be pushed to.
Applicable role
server
Responsible layer
Node.js 24.22.2/nghttp2 1.70.0 HTTP/2 framing implementation
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing. Node/nghttp2 rejects client PUSH_PROMISE before Achieve request dispatch.
Test evidence
http2-five-findings-investigation.md preserves the historical Node 22.15.0 GOAWAY(INTERNAL_ERROR) result. node24-adoption-decision.md and final Linux qualification run 42049611849 send client PUSH_PROMISE on Node 24.22.2 and observe the required connection GOAWAY(PROTOCOL_ERROR).
Assessment rationale
The released Achieve 3.1.0 / Node.js 24.22.2 endpoint applies the exact mandatory connection error when a client sends PUSH_PROMISE. The correction is in the runtime protocol layer; the malformed frame never reaches Achieve application logic.
Open question
The classification is specific to the qualified runtime profile and the direct receiving obligation.
V2 traceability
V2-H209

V3-9113-021 — RFC 9113 §6.7

Conformant Normative level: MUST

Requirement
A recipient of a PING frame without ACK MUST send a PING response with ACK and identical opaque data.
Conditions
Apply only under the conditions and exceptions stated in the cited section.
Applicable role
HTTP/2 recipient
Responsible layer
Node.js HTTP/2 session, stream, framing, and flow-control implementation
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
http2-frame-hpack-probes.md P03 sent non-ACK PING payload 3132333435363738 with an unknown extra flag; the server returned ACK PING with identical data and then served a valid request.
Assessment rationale
P03 directly established acknowledgment, byte-for-byte opaque-data identity, ignored unknown flag, and connection continuity.
Open question
No material uncertainty for this exact obligation.
V2 traceability
V2-H211;V2-NEW-060

V3-9113-022 — RFC 9113 §6.8

Conformant Normative level: MUST NOT

Requirement
After sending GOAWAY, an endpoint MUST NOT initiate new streams beyond the identified last stream and receivers apply the specified retry rules.
Conditions
GOAWAY direction, last-stream identifier, and retry conditions apply.
Applicable role
HTTP endpoint
Responsible layer
Node.js HTTP/2 session, stream, framing, and flow-control implementation
Implementation evidence
No Achieve path initiates HTTP/2 streams; Node owns GOAWAY/session state. achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
Achieve never calls pushStream or initiates request streams; no repository test exercises server-initiated streams.
Assessment rationale
The Achieve server never initiates request streams; Node owns GOAWAY and prevents new stream creation through its session API.
Open question
None for the established scope.
V2 traceability
V2-H205

V3-9113-023 — RFC 9113 §6.8

Conformant Normative level: MUST NOT

Requirement
A GOAWAY receiver MUST NOT initiate new streams with identifiers greater than the last-stream identifier.
Conditions
GOAWAY received.
Applicable role
HTTP endpoint
Responsible layer
Node.js HTTP/2 session, stream, framing, and flow-control implementation
Implementation evidence
No Achieve path initiates HTTP/2 streams after any GOAWAY; Node owns session state. achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
Achieve never calls pushStream or initiates request streams; no repository test exercises server-initiated streams.
Assessment rationale
As an origin server Achieve does not initiate request streams after receiving GOAWAY; no server push is used.
Open question
None for the established scope.
V2 traceability
V2-X065

V3-9113-024 — RFC 9113 §6.8

Not applicable Normative level: MAY

Requirement
Requests on streams greater than GOAWAY's last-stream identifier MAY be retried because they are known not to have been processed.
Conditions
Retry safety still follows HTTP method semantics.
Applicable role
client
Responsible layer
Node.js HTTP/2 session, stream, framing, and flow-control implementation
Implementation evidence
This retry permission concerns a request-initiating recipient; Achieve exposes an origin server, not an HTTP/2 client.
Test evidence
No focused repository test or raw-frame probe establishes this complete requirement.
Assessment rationale
The row describes retry permission for a request-initiating GOAWAY recipient. Achieve is assessed as an origin server and does not provide an HTTP/2 client.
Open question
None for the established scope.
V2 traceability
V2-X066

V3-9113-025 — RFC 9113 §6.9

Conformant Normative level: MUST

Requirement
Flow-control windows must not exceed 2^31−1; overflow is the specified stream or connection error.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
HTTP participant
Responsible layer
Node.js/nghttp2 flow-control implementation
Implementation evidence
achieve.js:1463-1512 delegates HTTP/2 framing and flow control to Node/nghttp2.
Test evidence
batch-e-evidence-review.md E03-E04.
Assessment rationale
Crossing the maximum on the connection produces GOAWAY FLOW_CONTROL_ERROR; crossing it on an open stream produces RST_STREAM FLOW_CONTROL_ERROR and preserves connection scope. Fragmented stream delivery agrees.
Open question
None for the tested overflow boundaries.
V2 traceability
V2-NEW-056

V3-9113-026 — RFC 9113 §6.9

Nonconformant Normative level: MUST

Requirement
WINDOW_UPDATE with increment zero is a PROTOCOL_ERROR at the applicable scope.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
HTTP participant
Responsible layer
Node.js HTTP/2 session, stream, framing, and flow-control implementation
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing. The focused investigation shows the malformed frames are rejected by Node/nghttp2 before Achieve request dispatch; standalone Node reproduces the wire result.
Test evidence
The focused investigation established both scopes. Final Node.js 24.22.2 Windows and Linux qualification observed the correct connection GOAWAY(PROTOCOL_ERROR), but a deliberately open nonzero stream still received GOAWAY(PROTOCOL_ERROR) instead of RST_STREAM(PROTOCOL_ERROR).
Assessment rationale
The qualified endpoint has corrected the connection-level code, but the remaining nonzero-stream scope defect persists in Node.js 24.22.2/nghttp2 1.70.0. RFC 9113 requires a stream error for a valid nonzero stream.
Open question
The Achieve immediate-response race can close a fragmented request stream before the invalid frame arrives; the standalone open-stream reproduction removes that artifact. Upstream nghttp2 correction remains unresolved.
V2 traceability
V2-NEW-062

V3-9113-027 — RFC 9113 §6.9

Conformant Normative level: MUST NOT

Requirement
A sender MUST NOT send a flow-controlled frame whose payload exceeds the available connection or stream window.
Conditions
DATA frame subject to both windows.
Applicable role
HTTP endpoint
Responsible layer
Node.js/nghttp2 HTTP/2 sender
Implementation evidence
achieve.js:1463-1512 delegates HTTP/2 framing and flow control to Node/nghttp2.
Test evidence
batch-e-evidence-review.md E05-E07.
Assessment rationale
A 100000-octet response stops at 65535 with both default windows, at 10 with an isolated stream window, and at 65535 with an isolated connection window; it resumes only after corresponding credit.
Open question
None for the tested independent send-window controls.
V2 traceability
V2-X049

V3-9113-028 — RFC 9113 §6.9

Unverified Normative level: MUST

Requirement
A receiver MUST treat flow-control window exceedance as FLOW_CONTROL_ERROR at the applicable scope.
Conditions
Peer exceeds connection or stream window.
Applicable role
HTTP endpoint
Responsible layer
Node.js/nghttp2 HTTP/2 receiver
Implementation evidence
achieve.js:1463-1512 delegates HTTP/2 framing and flow control to Node/nghttp2.
Test evidence
batch-e-evidence-review.md E08 establishes stream exceedance as RST_STREAM FLOW_CONTROL_ERROR. The final probe raised the stream window to 100,000, paused application consumption, and sent 65,535 and 65,536 DATA octets in contiguous and fragmented forms; Node emitted connection WINDOW_UPDATE credit and acknowledged a following PING in every case.
Assessment rationale
The stream branch conforms. A peer can violate a connection window in protocol terms, but the tested Node/nghttp2 receiver replenishes connection credit before exhaustion even when the application stream is paused. The attempted sends therefore remained within credit actually advertised on the wire and did not trigger the connection branch.
Open question
A conclusive connection-scope test needs a supported manual-flow-control mode or authoritative Node/nghttp2 evidence. Ignoring WINDOW_UPDATE credit or lowering unadvertised internal state would not be valid wire-conformance evidence.
V2 traceability
V2-X050

V3-9113-029 — RFC 9113 §6.9.2

Conformant Normative level: MUST

Requirement
A SETTINGS_INITIAL_WINDOW_SIZE change must adjust all active stream windows and handle overflow.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
HTTP participant
Responsible layer
Node.js 24.22.2/nghttp2 1.70.0 SETTINGS flow-control handling
Implementation evidence
achieve.js:1463-1512 delegates HTTP/2 SETTINGS and flow control to Node/nghttp2.
Test evidence
batch-e-evidence-review.md E10-E11 preserves the historical Node 22.15.0 wrong-scope result. node24-adoption-decision.md and final Linux qualification run 42049611849 adjust an active stream window through SETTINGS_INITIAL_WINDOW_SIZE to overflow and observe connection GOAWAY(FLOW_CONTROL_ERROR).
Assessment rationale
The released Achieve 3.1.0 / Node.js 24.22.2 endpoint correctly adjusts the active stream window and uses the required connection-scoped FLOW_CONTROL_ERROR for the previously failing overflow case.
Open question
The bounded probe establishes the demonstrated overflow boundary and valid controls, not every possible flow-control sequence.
V2 traceability
V2-NEW-059

V3-9113-030 — RFC 9113 §8.1

Conformant Normative level:

Requirement
A message whose Content-Length does not equal the sum of DATA payload lengths is malformed.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
HTTP participant
Responsible layer
Node.js HTTP/2 parser; Achieve handles requests after parsing
Implementation evidence
achieve.js:1463-1512 creates HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
batch-e-evidence-review.md E12-E13.
Assessment rationale
Exact length succeeds. Declared lengths both below and above four DATA octets receive RST_STREAM PROTOCOL_ERROR, and a later health stream succeeds; fragmented delivery agrees.
Open question
None for the tested request-message length conditions.
V2 traceability
V2-NEW-070

V3-9113-031 — RFC 9113 §8.1.1

Unverified Normative level: MUST

Requirement
A detected malformed HTTP/2 request MUST be treated as a stream error of type PROTOCOL_ERROR.
Conditions
The server MAY send an HTTP response before closing or resetting the stream; that permission is not part of the mandatory obligation classified here.
Applicable role
HTTP/2 server
Responsible layer
Node.js HTTP/2 parser; Achieve handles requests after parsing
Implementation evidence
achieve.js:1414-1424 resets malformed HTTP/2 target streams with NGHTTP2_PROTOCOL_ERROR; other malformed-message handling remains Node-owned.
Test evidence
http2-frame-hpack-probes.md P31-P47; batch-e-evidence-review.md E12-E14; tests/request_target_syntax/verify.js:55-90.
Assessment rationale
The corpus establishes PROTOCOL_ERROR and connection continuity for many malformed-field, pseudo-header, trailer, target, and Content-Length families, but the broad record still quantifies over every detected malformed request condition. The optional response permission is recorded only as a condition, not combined into the MUST.
Open question
Split the broad record into defined malformed-message families or add authoritative coverage for remaining detected conditions.
V2 traceability
V2-H215

V3-9113-032 — RFC 9113 §8.1.1

Not applicable Normative level: MUST

Requirement
A client MUST NOT accept a malformed HTTP/2 response, and a detected malformed response MUST be treated as a stream error of type PROTOCOL_ERROR.
Conditions
Requests can receive an HTTP error response or stream error; malformed responses require stream error.
Applicable role
HTTP/2 client/response recipient
Responsible layer
External HTTP/2 client
Implementation evidence
achieve.js:1414-1424 resets malformed HTTP/2 target streams with NGHTTP2_PROTOCOL_ERROR; other malformed-message handling remains Node-owned.
Test evidence
tests/request_target_syntax/verify.js:55-90 verifies protocol-error resets for malformed targets on h2c and h2, but not this complete malformed-field condition.
Assessment rationale
Achieve is assessed as an origin server, not an HTTP/2 response recipient.
Open question
None for Achieve origin-server scope.
V2 traceability
V2-H215

V3-9113-033 — RFC 9113 §8.2.1

Conformant Normative level: MUST

Requirement
HTTP/2 field names must be lowercase; uppercase names make the message malformed.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
HTTP endpoint
Responsible layer
Node.js HTTP/2 parser; Achieve handles requests after parsing
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
http2-frame-hpack-probes.md P31 sent uppercase field name X-Test; Node 22.15.0 returned stream PROTOCOL_ERROR and served a following request.
Assessment rationale
P31 directly exercised the uppercase-name prohibition and mandatory malformed-message handling with correct stream scope.
Open question
Other invalid field octets are separate ledger obligations; no material uncertainty remains for uppercase names.
V2 traceability
V2-NEW-067

V3-9113-034 — RFC 9113 §8.2.2

Conformant Normative level: MUST NOT

Requirement
An endpoint MUST NOT generate an HTTP/2 message containing connection-specific fields.
Conditions
Applies when the endpoint constructs an HTTP/2 message; includes Connection, Proxy-Connection, Keep-Alive, Transfer-Encoding, and Upgrade.
Applicable role
HTTP endpoint sender
Responsible layer
Node.js HTTP/2 response serializer and Achieve/application response logic
Implementation evidence
achieve.js:1463-1512 creates Node HTTP/2 servers and uses the compatibility response API; Node serializes response fields selected by Achieve or servlet applications.
Test evidence
The final-unverified probe attempted Connection, Keep-Alive, Proxy-Connection, Transfer-Encoding, and Upgrade through an Achieve servlet. Node dropped Connection with an UnsupportedWarning and emitted a normal response without it; the other attempts produced no response field section containing the prohibited field. A subsequent request on the session succeeded. Batch F independently established Transfer-Encoding serializer rejection.
Assessment rationale
Every connection-specific field named by section 8.2.2 was attempted through the supported response API, and none appeared on the wire. The serializer, not Achieve application logic, enforces the prohibition.
Open question
Rejected fields other than Connection prevent a normal application response; that operational behavior is outside this sender prohibition.
V2 traceability
V2-NEW-063

V3-9113-035 — RFC 9113 §8.2.2

Conformant Normative level: MUST

Requirement
An HTTP/2 message containing connection-specific fields is malformed and MUST be handled using the malformed-message rules.
Conditions
Includes Connection, Keep-Alive, Proxy-Connection, Transfer-Encoding, and Upgrade.
Applicable role
HTTP endpoint
Responsible layer
Node.js HTTP/2 parser; Achieve handles requests after parsing
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
http2-frame-hpack-probes.md P32-P36 sent Connection, Keep-Alive, Proxy-Connection, Transfer-Encoding, and Upgrade individually; every request received stream PROTOCOL_ERROR and every connection remained usable.
Assessment rationale
The probe set covers every field named by section 8.2.2 and observes the mandatory malformed-message handling at stream scope.
Open question
No material uncertainty for the named receiving cases on the assessed Node.js 22.15.0 endpoint.
V2 traceability
V2-S009

V3-9113-036 — RFC 9113 §8.2.2

Conformant Normative level: MUST NOT

Requirement
An HTTP/2 sender MUST NOT generate Transfer-Encoding, including chunked.
Conditions
HTTP/2 messages use frames, not transfer codings.
Applicable role
sender
Responsible layer
Node.js HTTP/2 response serializer and Achieve/application response logic
Implementation evidence
Node HTTP/2 serializes response frames; Achieve sets semantic headers/body but does not generate Transfer-Encoding. achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
tests/static_length/verify.js:100-180 verifies omission on h2c and h2; Batch F application attempts were rejected by the serializer with ERR_HTTP2_INVALID_CONNECTION_HEADERS and emitted no Transfer-Encoding field.
Assessment rationale
Ordinary output and an attempted prohibited application field establish that the centralized serializer does not generate Transfer-Encoding.
Open question
The rejected application attempt did not receive a normal response; this does not cause prohibited wire output.
V2 traceability
V2-X059

V3-9113-037 — RFC 9113 §8.2.2

Conformant Normative level: MUST NOT

Requirement
`TE` is permitted only with the value `trailers`; other values make the message malformed.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
HTTP participant
Responsible layer
Node.js HTTP/2 parser; Achieve handles requests after parsing
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
http2-frame-hpack-probes.md P37 sent TE: gzip and received stream PROTOCOL_ERROR; P38 sent TE: trailers and received a normal response.
Assessment rationale
The negative and positive controls directly establish the section 8.2.2 TE restriction and its sole permitted value.
Open question
No material uncertainty for the tested restriction; comma-combined alternatives would still contain a value other than trailers and are not needed to establish the rule.
V2 traceability
V2-NEW-068

V3-9113-038 — RFC 9113 §8.3

Conformant Normative level: MUST

Requirement
All pseudo-header fields must precede regular fields; a later pseudo-header makes the message malformed.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
HTTP participant
Responsible layer
Node.js HTTP/2 parser; Achieve handles requests after parsing
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
http2-frame-hpack-probes.md P39 placed :path after a regular field; Node 22.15.0 returned stream PROTOCOL_ERROR and served a following request.
Assessment rationale
P39 directly exercises the ordering prohibition and mandatory malformed-message treatment.
Open question
No material uncertainty for this exact obligation.
V2 traceability
V2-NEW-064

V3-9113-039 — RFC 9113 §8.3

Conformant Normative level: MUST

Requirement
Pseudo-header fields must appear only in their defined message context.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
HTTP participant
Responsible layer
Node.js/nghttp2 HTTP/2 field parser and sender
Implementation evidence
achieve.js:1463-1512 creates HTTP/2 servers; achieve.js:1407-1441 receives requests only after Node protocol parsing.
Test evidence
http2-frame-hpack-probes.md P47; batch-e-evidence-review.md E14.
Assessment rationale
A response pseudo-header in a request, an undefined pseudo-header, and a request pseudo-header in trailers each receive stream PROTOCOL_ERROR while the connection remains usable. Normal server responses use the defined :status context.
Open question
None for the defined request, response, undefined, and trailer contexts.
V2 traceability
V2-NEW-065

V3-9113-040 — RFC 9113 §8.3

Conformant Normative level: MUST NOT

Requirement
A message must not contain duplicate pseudo-header fields.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
HTTP participant
Responsible layer
Node.js HTTP/2 parser; Achieve handles requests after parsing
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
http2-frame-hpack-probes.md P40, P43, and P45 duplicated :method, :scheme, and :path respectively; each received stream PROTOCOL_ERROR and left the connection usable.
Assessment rationale
Three different pseudo-header names establish generic duplicate-pseudo-header enforcement and the required malformed-message handling.
Open question
A separate :authority duplicate is not necessary to establish the generic parser rule.
V2 traceability
V2-NEW-066

V3-9113-041 — RFC 9113 §8.3.1

Conformant Normative level: MUST

Requirement
For http or https URIs, :path MUST NOT be empty; OPTIONS in asterisk form uses '*' and classic CONNECT omits :path.
Conditions
HTTP or HTTPS requests, with the defined OPTIONS asterisk-form and classic CONNECT rules.
Applicable role
HTTP participant
Responsible layer
Node.js HTTP/2 parser; Achieve handles requests after parsing
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
http2-frame-hpack-probes.md P46 sent an empty :path on GET; Node 22.15.0 returned stream PROTOCOL_ERROR and served a following request. Existing tests/connect/verify.js exercises valid classic CONNECT.
Assessment rationale
P46 directly establishes rejection of the prohibited empty value. The RFC does not permit an empty OPTIONS value; it requires '*' for the asterisk form, while CONNECT omits :path.
Open question
No material uncertainty for the empty-path prohibition.
V2 traceability
V2-NEW-069

V3-9113-042 — RFC 9113 §8.3.1

Conformant Normative level: MUST

Requirement
A request MUST contain exactly one :method pseudo-header.
Conditions
All HTTP/2 requests.
Applicable role
HTTP endpoint
Responsible layer
Node.js HTTP/2 parser; Achieve handles requests after parsing
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
http2-frame-hpack-probes.md P40 and P41 sent duplicate and missing :method respectively; each received stream PROTOCOL_ERROR. Existing tests/connect/verify.js exercises a valid classic CONNECT request.
Assessment rationale
The absence and duplication controls directly establish the exactly-one :method requirement and malformed-message handling.
Open question
No material uncertainty for this exact obligation.
V2 traceability
V2-X051

V3-9113-043 — RFC 9113 §8.3.1

Conformant Normative level: MUST

Requirement
A non-CONNECT request MUST contain exactly one :scheme pseudo-header.
Conditions
Requests other than classic CONNECT.
Applicable role
HTTP endpoint
Responsible layer
Node.js HTTP/2 parser; Achieve handles requests after parsing
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
http2-frame-hpack-probes.md P42 and P43 sent missing and duplicate :scheme on non-CONNECT requests; each received stream PROTOCOL_ERROR.
Assessment rationale
Both failure modes directly establish exactly-one :scheme for the applicable non-CONNECT request class.
Open question
Classic CONNECT is excluded by the requirement condition.
V2 traceability
V2-X052

V3-9113-044 — RFC 9113 §8.3.1

Conformant Normative level: MUST

Requirement
A non-CONNECT request MUST contain exactly one :path pseudo-header with the defined nonempty/OPTIONS exception.
Conditions
Requests other than classic CONNECT.
Applicable role
HTTP endpoint
Responsible layer
Node.js HTTP/2 parser; Achieve handles requests after parsing
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
http2-frame-hpack-probes.md P44-P46 sent missing, duplicate, and empty :path on non-CONNECT requests; each received stream PROTOCOL_ERROR.
Assessment rationale
The probes directly establish the mandatory presence, uniqueness, and nonempty value for applicable non-CONNECT requests.
Open question
Classic CONNECT is excluded; the OPTIONS asterisk form is a required nonempty value, not an empty-path exception.
V2 traceability
V2-X053

V3-9113-045 — RFC 9113 §8.3.1

Conformant Normative level:

Requirement
A request that omits :authority must carry equivalent authority information where required by the target URI and Host semantics.
Conditions
Authority can come from :authority or Host subject to consistency and URI rules.
Applicable role
HTTP endpoint
Responsible layer
Shared: Node.js pseudo-header parsing and Achieve authority validation
Implementation evidence
achieve.js:1167-1253 validates HTTP/2 :authority and Host after Node pseudo-header parsing; achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
tests/http2_authority/verify.js:110-187 exercises :authority/Host combinations on h2c and h2; passed locally.
Assessment rationale
The authority suite demonstrates accepted authority-only and Host-only requests and rejects conflicts on h2c and h2.
Open question
None for the established scope.
V2 traceability
V2-X054

V3-9113-046 — RFC 9113 §8.3.2

Conformant Normative level: MUST

Requirement
A response must contain exactly one `:status` value with a valid three-digit status code.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
HTTP participant
Responsible layer
Node.js HTTP/2 response serializer and Achieve/application response logic
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
tests/response_completion/verify.js:79-105,133-278 verifies final responses and stream completion on h2c and h2.
Assessment rationale
Node serializes the single status selected by Achieve; ordinary and error response suites demonstrate valid final status fields on both transports.
Open question
None for the established scope.
V2 traceability
V2-NEW-071

V3-9113-047 — RFC 9113 §8.3.2

Conformant Normative level: MAY

Requirement
A server MAY send one or more informational responses before exactly one final response.
Conditions
Before exactly one final response.
Applicable role
server
Responsible layer
Node.js HTTP/2 response serializer and Achieve/application response logic
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
Batch F sent 100 and 103 HEADERS without END_STREAM followed by exactly one final 200 and DATA; tests/response_completion/verify.js separately verifies final response completion.
Assessment rationale
The optional capability is implemented and the observed sequence follows section 8.3.2.
Open question
The observation covers the supported compatibility response API, not arbitrary socket manipulation by applications.
V2 traceability
V2-X057;V2-H223

V3-9113-048 — RFC 9113 §8.3.2

Conformant Normative level: MUST

Requirement
A server MUST send exactly one final response containing exactly one :status pseudo-header.
Conditions
Every accepted HTTP/2 request not terminated by connection/stream error.
Applicable role
server
Responsible layer
Node.js HTTP/2 response serializer and Achieve/application response logic
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
tests/response_completion/verify.js:79-105,133-278 verifies final responses and stream completion on h2c and h2.
Assessment rationale
Response-completion tests demonstrate exactly one final response for exercised accepted requests on h2c and h2, including failure paths and subsequent health checks.
Open question
None for the established scope.
V2 traceability
V2-X058

V3-9113-049 — RFC 9113 §8.5

Conformant Normative level: MUST

Requirement
Classic CONNECT MUST include :method CONNECT and :authority.
Conditions
Classic CONNECT only.
Applicable role
HTTP endpoint
Responsible layer
Node.js HTTP/2 parser; Achieve handles requests after parsing
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
tests/connect/verify.js:153-172 exercises a valid classic CONNECT; Batch F raw HPACK controls reached the handler when valid and received stream PROTOCOL_ERROR when :authority was omitted.
Assessment rationale
Positive and malformed controls directly establish required classic CONNECT fields on the tested endpoint.
Open question
Evidence is bounded to Node.js 22.15.0/nghttp2 1.64.0.
V2 traceability
V2-X055

V3-9113-050 — RFC 9113 §8.5

Conformant Normative level: MUST NOT

Requirement
Classic CONNECT MUST NOT include :scheme or :path.
Conditions
Classic CONNECT only.
Applicable role
HTTP endpoint
Responsible layer
Node.js HTTP/2 parser; Achieve handles requests after parsing
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
Batch F raw HPACK probes containing :scheme or :path each received stream RST_STREAM PROTOCOL_ERROR; the valid omission control reached the handler.
Assessment rationale
Both prohibited classic CONNECT pseudo-fields are directly rejected at the required stream scope.
Open question
Evidence is bounded to Node.js 22.15.0/nghttp2 1.64.0.
V2 traceability
V2-X056

V3-9113-051 — RFC 9113 §9.2

Conformant Normative level: MUST

Requirement
HTTP/2 over TLS must use TLS 1.2 or later, subject to the section's deployment requirements.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
HTTP endpoint
Responsible layer
TLS/OpenSSL and Node.js HTTP/2; Achieve supplies server options
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
Existing h2 tests establish successful TLS/ALPN h2 connections; no focused TLS-version, compression, renegotiation, or prohibited-cipher probe exists.
Assessment rationale
Node 22 defaults to TLS 1.2 minimum, and the secure HTTP/2 suites establish successful supported h2 operation without an older TLS mode configured by Achieve.
Open question
None for the established scope.
V2 traceability
V2-NEW-073

V3-9113-052 — RFC 9113 §9.2

Conformant Normative level: MUST

Requirement
TLS compression must be disabled for HTTP/2.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
HTTP endpoint
Responsible layer
TLS/OpenSSL and Node.js HTTP/2; Achieve supplies server options
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
Existing h2 tests establish successful TLS/ALPN h2 connections; no focused TLS-version, compression, renegotiation, or prohibited-cipher probe exists.
Assessment rationale
The Node/OpenSSL stack used by the supported endpoint has TLS compression disabled; Achieve exposes no option that enables it.
Open question
None for the established scope.
V2 traceability
V2-NEW-074

V3-9113-053 — RFC 9113 §9.2.1

Nonconformant Normative level: MUST

Requirement
After the client connection preface, a TLS 1.2 renegotiation attempt MUST be treated as a connection error of type PROTOCOL_ERROR; the narrow client-certificate exception is available only before the preface.
Conditions
TLS 1.2 HTTP/2; renegotiation after the client connection preface.
Applicable role
HTTP endpoint
Responsible layer
TLS/OpenSSL and Node.js HTTP/2; Achieve supplies server options
Implementation evidence
achieve.js:1463-1512 creates TLS Node HTTP/2 servers and passes the supplied TLS options to Node.
Test evidence
Final Node.js 24.22.2 Windows and Linux qualification forced TLS 1.2, negotiated ALPN h2, completed the client preface, and initiated renegotiation. Node rejected it with ERR_TLS_RENEGOTIATION_DISABLED, but no GOAWAY(PROTOCOL_ERROR) was observed; a subsequent PING was not acknowledged.
Assessment rationale
Renegotiation is disabled, but the qualified endpoint does not emit the mandatory HTTP/2 connection error of type PROTOCOL_ERROR.
Open question
The pre-preface client-certificate exception was not exercised and does not apply to the tested sequence.
V2 traceability
V2-NEW-075

V3-9113-054 — RFC 9113 §9.2.1

Conformant Normative level: MUST

Requirement
A TLS implementation for HTTP/2 MUST support ALPN negotiation of the h2 protocol identifier.
Conditions
HTTP/2 over TLS.
Applicable role
HTTP endpoint
Responsible layer
TLS/OpenSSL and Node.js HTTP/2; Achieve supplies server options
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
Existing h2 tests establish successful TLS/ALPN h2 connections; no focused TLS-version, compression, renegotiation, or prohibited-cipher probe exists.
Assessment rationale
Secure HTTP/2 connections made by Node clients negotiate h2 successfully, establishing ALPN h2 support.
Open question
None for the established scope.
V2 traceability
V2-X060

V3-9113-055 — RFC 9113 §9.2.1

Conformant Normative level: MUST

Requirement
A server that selects HTTP/2 over TLS MUST select the h2 ALPN identifier before using HTTP/2.
Conditions
TLS negotiation chooses HTTP/2.
Applicable role
server
Responsible layer
TLS/OpenSSL and Node.js HTTP/2; Achieve supplies server options
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
Existing h2 tests establish successful TLS/ALPN h2 connections; no focused TLS-version, compression, renegotiation, or prohibited-cipher probe exists.
Assessment rationale
The secure suites reach HTTP/2 request handling only after Node selects h2 by ALPN.
Open question
None for the established scope.
V2 traceability
V2-X061

V3-9113-056 — RFC 9113 §9.2.2

Nonconformant Normative level: SHOULD NOT

Requirement
A TLS 1.2 HTTP/2 endpoint SHOULD NOT negotiate a cipher suite on the prohibited list.
Conditions
TLS 1.2 only.
Applicable role
HTTP endpoint
Responsible layer
TLS/OpenSSL and Node.js HTTP/2; Achieve supplies server options
Implementation evidence
achieve.js:1463-1512 passes secure-server TLS options to Node without applying the RFC 9113 prohibited-cipher list.
Test evidence
Final Node.js 24.22.2/OpenSSL 3.5.9 Windows and Linux qualification explicitly configured TLS_RSA_WITH_AES_128_CBC_SHA with security level 0; TLS 1.2 and ALPN h2 negotiated and the endpoint sent HTTP/2 SETTINGS. The mandatory-cipher control also negotiated h2.
Assessment rationale
The qualified endpoint permits an explicitly configured cipher on RFC 9113's prohibited list, missing the SHOULD NOT recommendation.
Open question
The prohibited case requires explicit opt-in and lowered OpenSSL security policy; default cipher selection was not implicated.
V2 traceability
V2-X067

V3-9113-057 — RFC 9113 §9.2.2

Optional not implemented Normative level: MAY

Requirement
An endpoint MAY treat negotiation of a prohibited TLS 1.2 cipher suite as a connection error of type INADEQUATE_SECURITY.
Conditions
Prohibited TLS 1.2 cipher negotiated.
Applicable role
HTTP endpoint
Responsible layer
TLS/OpenSSL and Node.js HTTP/2; Achieve supplies server options
Implementation evidence
achieve.js:1463-1512 passes secure-server TLS options to Node and does not add a prohibited-cipher detector.
Test evidence
Batch F negotiated a prohibited TLS 1.2 suite with ALPN h2 and received server SETTINGS rather than GOAWAY INADEQUATE_SECURITY.
Assessment rationale
RFC 9113 permits but does not require this error; absence of the optional behavior is not nonconformance.
Open question
The later GOAWAY in the combined TLS probe was caused by a separate renegotiation attempt, not cipher detection.
V2 traceability
V2-X068

V3-9113-058 — RFC 9113 §10.3

Not applicable Normative level: MUST

Requirement
An intermediary translating an HTTP/2 request or response to another HTTP version MUST validate fields according to RFC 9113 section 8.2 before translation.
Conditions
The implementation acts as an intermediary and translates an HTTP/2 message to another HTTP version.
Applicable role
HTTP intermediary
Responsible layer
Not Achieve in its supported origin-server role
Implementation evidence
Achieve operates as an origin server and does not translate or forward HTTP/2 messages to another HTTP version.
Test evidence
P25-P30 concern HPACK decoding errors and compression-context isolation; they do not exercise intermediary protocol translation and are not evidence for this corrected requirement.
Assessment rationale
RFC 9113 section 10.3 contains this intermediary validation obligation, not the former HPACK-context requirement. Achieve does not perform the conditional intermediary translation role.
Open question
None for Achieve's supported origin-server role. HPACK decoding errors remain covered by V3-9113-006; descriptive per-connection compression state does not create a separate section 10.3 endpoint obligation.
V2 traceability
V2-X064

V3-9113-059 — RFC 9113 §10.5.1

Conformant Normative level: MUST

Requirement
An implementation MUST process a field block sufficiently to maintain a consistent connection state unless the connection is closed.
Conditions
Applies when an implementation declines to retain or otherwise use an excessive field section; closing the connection is the alternative permitted by the requirement.
Applicable role
HTTP endpoint
Responsible layer
Node.js HTTP/2/nghttp2 field-block processing; Achieve receives requests only after protocol parsing
Implementation evidence
achieve.js:1463-1512 creates cleartext or TLS Node HTTP/2 servers; achieve.js:1407-1441 receives compatibility-API requests only after Node protocol parsing.
Test evidence
A raw HPACK probe sent 130 incrementally indexed fields, ending with x-marker, in an excessive request block. Node reset stream 1 with ENHANCE_YOUR_CALM, kept the connection open, then decoded stream 3 using dynamic index 62 for that newest marker and returned 200 without COMPRESSION_ERROR.
Assessment rationale
The dependent second block could be decoded only if the rejected first block had still been processed sufficiently to update the shared HPACK state. The continuing connection therefore remained consistent after the excessive field section.
Open question
This establishes the required state behavior for the tested excessive-field path on Node.js 22.15.0/nghttp2 1.64.0, not every resource-exhaustion strategy.
V2 traceability
V2-X062

V3-9113-060 — RFC 9113 §10.5.2

Conformant Normative level: SHOULD

Requirement
An implementation SHOULD track use of features that expose work and resource commitments and set limits on their use.
Conditions
Features that expose implementation work or resource commitment.
Applicable role
HTTP endpoint
Responsible layer
Node.js HTTP/2/nghttp2 resource controls; Achieve uses defaults
Implementation evidence
achieve.js:1463-1512 creates Node HTTP/2 servers without disabling the runtime's finite session-memory, header-pair, settings, invalid-frame, rejected-stream, and outstanding-operation defaults.
Test evidence
Node 22 HTTP/2 documentation specifies finite server-side defaults including 10 MiB session memory, 128 header pairs, 32 settings entries, 100 rejected streams, and 1000 invalid frames. Batch F's bounded request exercise established continued service but is not treated as proof for every resource-exposure feature.
Assessment rationale
Documented finite server-side controls establish the section's recommendation for the assessed runtime configuration. The prior client-side outstanding-ping observation is not used as evidence of server-side resistance.
Open question
This classification is not a claim of universal denial-of-service immunity or proof for every possible feature interaction.
V2 traceability
V2-X063

V3-9113-061 — RFC 9113 §9.2.2

Conformant Normative level: MUST

Requirement
A deployment of HTTP/2 over TLS 1.2 MUST support TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 with the P-256 elliptic curve.
Conditions
Applies when HTTP/2 is deployed over TLS 1.2.
Applicable role
HTTP/2 TLS deployment
Responsible layer
Node.js/OpenSSL TLS configuration used by Achieve secure HTTP/2 servers
Implementation evidence
achieve.js:1463-1512 passes secure-server TLS options to Node.
Test evidence
A focused Achieve secure-HTTP/2 control constrained both peers to TLS 1.2, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, P-256 only, and ALPN h2. The handshake succeeded; getEphemeralKeyInfo reported ECDH prime256v1, 256 bits.
Assessment rationale
Successful negotiation with both the mandatory cipher and an exclusively P-256 ephemeral-key configuration directly establishes support on the tested Node.js 22.15.0/OpenSSL 3.0.16 deployment.
Open question
Deployment options can select other policies; this classification establishes the required supported combination, not conformance of every operator-supplied TLS configuration.
V2 traceability
No V2 predecessor recorded.

V3-9113-062 — RFC 9113 §9.2.1

Conformant Normative level: MUST

Requirement
A deployment of HTTP/2 over TLS 1.2 MUST disable renegotiation.
Conditions
Applies to HTTP/2 over TLS 1.2. The distinct post-preface PROTOCOL_ERROR response obligation remains in V3-9113-053.
Applicable role
HTTP/2 TLS endpoint
Responsible layer
Node.js/OpenSSL secure HTTP/2 implementation
Implementation evidence
achieve.js:1463-1512 delegates TLS and HTTP/2 protocol handling to Node/OpenSSL/nghttp2; Achieve contains no server-initiated renegotiation path.
Test evidence
Final Node.js 24.22.2 Windows and Linux qualification forced TLS 1.2, completed ALPN h2 and the connection preface, then initiated TLS renegotiation. Node rejected the attempt with ERR_TLS_RENEGOTIATION_DISABLED. The missing compliant HTTP/2 error handling remains separately Nonconformant under V3-9113-053.
Assessment rationale
Implementation inspection excludes an Achieve server-initiated renegotiation path, and the focused client-initiated attempt was rejected. Together these establish disablement for the assessed deployment while keeping the distinct error-code defect separate.
Open question
The result is specific to Node.js 24.22.2/OpenSSL 3.5.9 and should be repeated when that runtime baseline changes.
V2 traceability
V2-NEW-075