# Achieve 3.1.0 HTTP Standards Conformance Summary

## Scope
This summary covers the corrected V3 inventory for RFC 9110 HTTP Semantics, RFC 9111 HTTP Caching, RFC 9112 HTTP/1.1, and RFC 9113 HTTP/2. The authoritative runtime profile is released Achieve 3.1.0 on the specifically qualified Node.js 24.22.2 runtime (OpenSSL 3.5.9, nghttp2 1.70.0, llhttp 9.4.3). Release v3.1.0 resolves to merge commit 3f0dd82bdc2873c231ac53fd51ceadaa06eef7d0; final Linux qualification run 42049611849 exercised clean candidate commit d1efa3070a290374f8058f0f80db539f34101897. Earlier Node.js 22.15.0 observations remain historical evidence and identify runtime-layer corrections rather than being rewritten.

## Results
Of 211 requirements, 163 are Conformant, 9 Nonconformant, 8 Unverified, 22 Not applicable, and 9 Optional not implemented. These totals describe available evidence, not a percentage conformance score.

## Verified behavior
- Achieve implements tested HTTP method, request-target, authority, conditional request, range, representation metadata, static-resource, response-completion, and application-containment behavior across its applicable transports.
- Application-selected 205 responses suppress managed and application-owned content across HTTP, HTTPS, h2c, and secure HTTP/2 while retaining native argument validation, lifecycle errors, callback behavior, zero-length framing, and subsequent connection use.
- Successful matching `If-Range` single-part 206 responses omit redundant `Content-Type` and `Last-Modified` metadata while retaining the current strong `ETag`, `Date`, `Content-Range`, partial `Content-Length`, `Accept-Ranges`, `Server`, and exact requested bytes across HTTP, HTTPS, h2c, and secure HTTP/2. Ordinary 206 and false-condition 200 responses retain their normal metadata.
- HTTP/1.1 parsing and serialization are primarily Node-owned; focused raw probes establish many framing, rejection, closure, and pipelining cases.
- HTTP/2 h2c and h2 application behavior is verified for ordinary requests, authority handling, response completion, target rejection, lengths, and ALPN-based secure operation. Focused h2c raw-frame probes additionally establish selected malformed-frame, SETTINGS, stream-identifier, PUSH_PROMISE, and WINDOW_UPDATE behavior on the tested runtimes; untested exceptional states are not inferred from those results.
- Batch A review of the existing raw-frame evidence establishes 14 additional RFC 9113 requirements without new probes: oversized-frame handling, unknown frame types, HPACK decode failures, SETTINGS ACK sizing, PING acknowledgement, uppercase and connection-specific request fields, TE restrictions, pseudo-header ordering and duplication, and mandatory request pseudo-headers. Receiver-side field-block probes did not establish the distinct sender obligation for contiguous field-block transmission.
- Batch B verifies per-request independence, core field/trailer behavior, request-trailer separation, 200/206/304 metadata retention, and 304 metadata minimization across HTTP/1.1 and h2c. Conditional 401 and 409 duties belong to servlet applications because Achieve core generates neither status.
- Batch C raw HTTP/1.1 probes on Node.js 22.15.0 establish field-specific repeated-line handling, appropriate rejection of individual and aggregate field overflow, and immediate `100-continue` behavior before request content. Standalone Node comparisons assign those parser and expectation behaviors to Node's HTTP layer. Five broad sender/recipient obligations remain Unverified rather than being inferred from the bounded corpus.
- Batch D resolves the remaining RFC 9112 records using raw TCP, fragmented chunk input, standalone Node controls, and TLS record/abort observations. Response grammar, octet parsing, chunk-extension handling, trailer separation, server `close_notify`, and incomplete-client-close tolerance conform on the tested stack. Unrecognized transfer coding followed by valid final chunked is accepted instead of receiving the recommended 501.
- Batch E resolves nine HTTP/2 stream-state and flow-control records. Independent stream and connection send windows, padding accounting, maximum-window overflow, active-window adjustment, Content-Length mismatch handling, pseudo-header contexts, and stream-identifier ordering were verified with controlled raw frames. Four broad or conditionally unreachable records remain Unverified rather than receiving inferred passes.
- Batch F resolves all nine originally assigned HTTP/2 output, CONNECT, TLS, and resource records. It verifies bounded sender reserved-bit handling, Transfer-Encoding exclusion, informational responses, classic CONNECT validation, and documented concrete resource bounds. The later quality review adds two distinct TLS obligations and corrects the section 10.5.1 field-block obligation without treating the earlier bounded evidence as proof of those requirements.
- The final Unverified investigation directly resolves six additional HTTP/2 records. Raw capture establishes contiguous server HEADERS/CONTINUATION output, dynamic stream-limit reduction allows existing streams to complete, every named connection-specific response field is suppressed or rejected, and a dependent HPACK block proves connection-state consistency after rejecting an excessive field section. TLS 1.2 negotiation establishes the mandatory cipher with P-256, while existing renegotiation rejection plus implementation inspection establishes disablement separately from the already-recorded wrong GOAWAY error code.
- Final Node.js 24.22.2 Linux qualification executed all 37 verifier suites with 37 passes, zero failures, and zero environmental skips; the package install/startup smoke test passed. Its bounded protocol artifact recorded six corrected observations, seven known limitations, and zero unexpected failures. Four requirement-level Node 22 nonconformities are now Conformant on the released runtime: V3-9113-008, V3-9113-019, V3-9113-020, and V3-9113-029.
- Achieve is an origin server, not an HTTP cache. Cache storage/reuse duties and client/proxy-only requirements are explicitly out of scope rather than counted as implementation successes.

## Known limitations
An HTTP/1.1 request-target that exceeds Node.js shared parser limits receives 431 rather than the RFC 9112 section 3 required 414. The behavior is inherited from Node.js shared `HPE_HEADER_OVERFLOW` handling and is reproduced on Node.js 22.15.0, 24.22.1, and the qualified 24.22.2 release runtime. Increasing `maxHeaderSize` is not a complete correction, PR #25605 only introduced generic 431 handling, and Achieve will not add a second HTTP request-line parser. The limitation remains a confirmed Nonconformant result; no new upstream issue has been filed.

Six RFC 9113 requirements remain Nonconformant on the assessed Achieve 3.1.0 / Node.js 24.22.2 endpoint: composite state/error record `V3-9113-007`, excess concurrent-stream handling `V3-9113-012`, stream-error framing `V3-9113-015`, stream-scoped zero-increment WINDOW_UPDATE handling `V3-9113-026`, post-preface TLS 1.2 renegotiation error signaling `V3-9113-053`, and prohibited TLS 1.2 cipher policy `V3-9113-056`. They represent fewer underlying Node/nghttp2/TLS causes, not six independent Achieve implementation bugs. The historical Node 22 wrong-code findings for `V3-9113-008`, `V3-9113-019`, and `V3-9113-020`, plus the wrong-scope active-window overflow finding `V3-9113-029`, are corrected on Node 24.22.2 and are now Conformant. The connection-level facet of `V3-9113-026` is also corrected, but its demonstrated stream-scope defect remains.

One RFC 9110 requirement remains Nonconformant on Node.js 24.22.2. Final qualification confirms that valid classic HTTP/2 CONNECT receives a Node-generated 405 without the Allow field required by section 15.5.6. The CONNECT result is Node-owned at the implementation layer but remains part of the supported endpoint's conformance result. The former findings `V3-9110-086` and `V3-9110-088` are Conformant in Achieve 3.1.0 after focused four-transport corrections and regression coverage for 205 content suppression and matching `If-Range` 206 metadata selection, respectively.

One additional RFC 9112 SHOULD-level nonconformity remains on Node.js 24.22.2. A request carrying an unrecognized transfer coding followed by final `chunked` receives 200 and its chunk-decoded bytes reach the application without decoding the unknown coding, rather than receiving the recommended 501. The behavior remains assigned to Node's HTTP parser. The separate request-target 431/414 result remains the RFC 9112 MUST-level finding.

## Unverified areas
- Exhaustive field syntax and application-authored response edge cases under RFC 9110.
- Remaining HTTP/2 uncertainty is limited to the broad connection-error and malformed-request universals and deterministic connection receive-window exceedance. Dynamic limit reduction, mandatory TLS 1.2 P-256 cipher support, renegotiation disablement, and field-block state consistency after rejection now have direct evidence on the tested runtime.
- HTTP/2 sender-side contiguous field-block transmission remains Unverified. Transfer-Encoding exclusion is now directly established; the former section 10.3 HPACK-context row was corrected to the actual intermediary translation requirement and is Not applicable to Achieve's origin-server role.
- RFC 9110 §15.5.9 contains no normative recommendation to send `Connection: close` with 408; the inherited V3 row was corrected to a traceable Not applicable inventory record. Node 22.15.0 nevertheless emitted that field and closed the connection in the bounded Batch C timeout observation.

## Optional unsupported features
The inventory distinguishes permitted absence from nonconformance. Examples include successful CONNECT tunneling and multipart byte-range generation where the relevant optional capability is not implemented. Achieve core also does not generate optional RFC 9111 Cache-Control directive forms assessed in the inventory.

## External dependencies
The complete endpoint depends on Node.js 24.22.2 HTTP/1.1 and HTTP/2 parsers, llhttp 9.4.3, nghttp2 1.70.0/HPACK and stream processing, and OpenSSL 3.5.9 including ALPN. Delegation does not make an obligation inapplicable; it determines responsibility and what evidence is needed.

## Verification priorities
1. Seek an upstream Node.js request-target overflow distinction that permits 414 without a second parser.
2. Preserve the bounded HTTP/2 probe corpus and repeat it when the supported Node/nghttp2 baseline changes; investigate remaining stream-state and HPACK scope only through similarly focused probes.
3. Retain TLS closure-alert, renegotiation, ALPN, and cipher probes when the Node/OpenSSL baseline changes; the present TLS classifications are version-specific.
4. Complete focused HTTP field, trailer, informational-response, and application-authored response checks where V3 remains Unverified.
