Achieve 3.1.0 HTTP Conformance Summary
The authoritative inventory contains 211 requirements. Totals describe the available evidence and are not a percentage conformance score.
| Classification | Requirements |
|---|---|
| Conformant | 163 |
| Nonconformant | 9 |
| Unverified | 8 |
| Not applicable | 22 |
| Optional not implemented | 9 |
| Total | 211 |
Verified release baseline
Release v3.1.0 resolves to merge commit 3f0dd82bdc2873c231ac53fd51ceadaa06eef7d0. Final Linux qualification run 42049611849 evaluated the clean release candidate with Node.js 24.22.2, OpenSSL 3.5.9, nghttp2 1.70.0, and llhttp 9.4.3.
The qualification passed 37 of 37 verifier suites, with zero failures and zero environmental skips. It also passed package installation and startup smoke testing. Earlier Node.js 22 findings remain historical evidence where a runtime upgrade changed behavior.
Nonconformant requirements (9)
These are requirement-level findings. Multiple records can share one underlying Node.js, nghttp2, or TLS cause, and a runtime-owned defect is not automatically an Achieve implementation defect.
V3-9110-098— An origin server generating a 405 response MUST generate an Allow field listing the target resource's currently supported methods. (Node.js HTTP/2 compatibility layer; complete Achieve endpoint)V3-9112-006— A server that receives a request-target longer than any URI it wishes to parse MUST respond with 414 (URI Too Long). (Node.js HTTP/1.1 parser and the complete Achieve endpoint)V3-9112-017— A server receiving an unrecognized request transfer coding should respond 501. (Node.js HTTP parser/Achieve endpoint)V3-9113-007— An endpoint MUST enforce the state-dependent permitted frame types and apply the specified stream or connection error for violations. (Node.js HTTP/2 session, stream, framing, and flow-control implementation)V3-9113-012— A receiver MUST treat a newly opened stream that exceeds its advertised maximum-concurrent-streams limit as the specified stream error. (Node.js 24.22.2/nghttp2 1.70.0 stream-concurrency handling)V3-9113-015— An endpoint detecting a stream error MUST send RST_STREAM with the applicable error code, subject to the closed-stream exceptions. (Node.js 24.22.2/nghttp2 1.70.0 stream-error handling)V3-9113-026— WINDOW_UPDATE with increment zero is a PROTOCOL_ERROR at the applicable scope. (Node.js HTTP/2 session, stream, framing, and flow-control implementation)V3-9113-053— 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. (TLS/OpenSSL and Node.js HTTP/2; Achieve supplies server options)V3-9113-056— A TLS 1.2 HTTP/2 endpoint SHOULD NOT negotiate a cipher suite on the prohibited list. (TLS/OpenSSL and Node.js HTTP/2; Achieve supplies server options)
Unverified requirements (8)
These remain unresolved because the available evidence is incomplete, broad obligations cannot be proven by bounded examples, or a specialized state has not been established reliably.
V3-9110-001— A sender must not generate protocol elements that violate the corresponding ABNF. (Shared/Node/Achieve)V3-9110-002— A sender must not generate syntax allowed only for a role it does not have. (Shared)V3-9110-003— Recipients should parse defensively with only marginal assumptions about conformance and size. (Node/shared)V3-9110-004— A recipient must accept elements at least as long as values it generates for the same elements. (Node/shared)V3-9110-005— A recipient must interpret received elements according to defined semantics absent a justified compatibility workaround. (Shared)V3-9113-014— An endpoint detecting a connection error SHOULD send GOAWAY with the applicable error code before closing when possible. (Node.js HTTP/2 session, stream, framing, and flow-control implementation)V3-9113-028— A receiver MUST treat flow-control window exceedance as FLOW_CONTROL_ERROR at the applicable scope. (Node.js/nghttp2 HTTP/2 receiver)V3-9113-031— A detected malformed HTTP/2 request MUST be treated as a stream error of type PROTOCOL_ERROR. (Node.js HTTP/2 parser; Achieve handles requests after parsing)
Interpretation limits
- Achieve is an origin server, not an HTTP cache. Cache-only duties are classified by applicability rather than counted as successes.
- Optional unsupported capabilities are separated from failures.
- Application-authored servlet responses remain the application's responsibility where Achieve neither generates nor prevents the relevant field or status.
- The current results are runtime-specific. A later Node.js, nghttp2, llhttp, or OpenSSL baseline requires regression qualification.
See the authoritative Markdown summary and remediation plan for the detailed evidence narrative.