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 42 authoritative V3 requirements for RFC 9112. Requirement text is a traceable summary; the linked RFC Editor section supplies the controlling normative text and conditions.
| Classification | Count |
|---|
| Conformant | 31 |
| Nonconformant | 2 |
| Unverified | 0 |
| Not applicable | 8 |
| Optional not implemented | 1 |
| Total | 42 |
|---|
Review the overall findings · Read the methodology · Inspect evidence sources
Conformant Normative level: MUST
- Requirement
- An HTTP/1.1 sender MUST generate messages conforming to the HTTP-message grammar and use the protocol version appropriate to that syntax.
- Conditions
- Version-specific sender conditions in RFC 9112 §2.2 apply.
- Applicable role
- sender
- Responsible layer
- Node.js HTTP sender; Achieve selects status, fields, and body
- Implementation evidence
- Node http.Server centrally serializes ordinary responses created at achieve.js:1559-1591; Achieve's fixed CONNECT response template at achieve.js:1255-1264 uses an HTTP/1.1 status line, CRLF field framing, explicit Content-Length, and Connection close.
- Test evidence
- Batch D byte-level capture validated representative static 200, missing-resource 404, parser 400, HTTP/1.0-request, Content-Length, chunked, field-name, and status-line output. Node rejected attempted invalid field syntax rather than serializing it.
- Assessment rationale
- For Achieve core output through supported Node response APIs, representative wire checks plus the centralized serializer and fixed direct template support Conformant. This is not an exhaustive proof of every grammar production or arbitrary application socket output.
- Open question
- Bounded to tested core paths and supported response APIs on Node.js 22.15.0; direct application socket writes remain application responsibility.
- V2 traceability
- V2-H101
Conformant Normative level: MUST
- Requirement
- An HTTP/1.1 recipient MUST parse messages as an octet sequence in an encoding that is a superset of US-ASCII.
- Conditions
- Parsing as Unicode without octet boundaries is unsafe.
- Applicable role
- recipient
- Responsible layer
- Node.js HTTP parser
- Implementation evidence
- Requests reach Achieve only after Node's native HTTP parser delineates request lines and fields at achieve.js:1407-1441 and 1559-1591.
- Test evidence
- A Batch D raw field-value control used octets 0x80, 0xff, 0xc2, and 0x85. Achieve and standalone Node preserved one octet per exposed code unit instead of UTF-8-decoding 0xc2 0x85; a high-bit field-name octet was rejected with 400.
- Assessment rationale
- The direct controls support octet-oriented parsing for the tested request-line/field parser boundary on Node.js 22.15.0. They do not independently enumerate every request component or future parser implementation.
- Open question
- Bounded to the tested components and Node.js 22.15.0; runtime parser changes require reassessment.
- V2 traceability
- V2-H102
Conformant Normative level: SHOULD
- Requirement
- A server receiving one or more empty lines before a request-line SHOULD ignore at least one such line.
- Conditions
- Leading CRLF before request-line.
- Applicable role
- server
- Responsible layer
- Node.js HTTP parser
- Implementation evidence
- achieve.js:1407-1441, 1559-1591 (Node HTTP server delegates parsed requests to achieveApp)
- Test evidence
- No pre-existing focused assertion. Runtime probe: Raw TCP: leading CRLF before GET produced 200 and the expected body; connection closed normally.
- Assessment rationale
- The supported Node 22.15 endpoint ignored at least one leading empty line as recommended.
- Open question
- Repeat on other supported Node 22 patch levels if runtime-matrix assurance is required.
- V2 traceability
- V2-X031
Conformant Normative level: MUST
- Requirement
- A server receiving whitespace between request-line and first field must reject the request or consume and ignore each whitespace line.
- 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 parser
- Implementation evidence
- achieve.js:1407-1441, 1559-1591 (Node HTTP server delegates parsed requests to achieveApp)
- Test evidence
- No pre-existing focused assertion. Runtime probe: Raw TCP: whitespace-preceded line after request-line produced 400 and Connection: close.
- Assessment rationale
- Rejection is one of the two permitted behaviors.
- Open question
- None for the probed runtime.
- V2 traceability
- V2-NEW-036
Conformant Normative level:
- Requirement
- An HTTP/1.1 request-line has the grammar method SP request-target SP HTTP-version; recipients parse those components before field processing.
- Conditions
- Malformed request-line handling is recorded separately.
- Applicable role
- server
- Responsible layer
- Node.js HTTP parser; Achieve validates target after parsing
- Implementation evidence
- achieve.js:1098-1145, 1407-1433 (Achieve validates parsed request-target and authority)
- Test evidence
- tests/request_target_syntax/verify.js:12-101 (raw HTTP/HTTPS and HTTP/2 target checks; 560 checks) Runtime probe: Raw valid requests were parsed; malformed request-line cases were rejected with 400.
- Assessment rationale
- Observed parsing follows the request-line component model and malformed input does not reach application dispatch.
- Open question
- The ledger row states grammar rather than a discrete BCP 14 obligation.
- V2 traceability
- V2-H104
Nonconformant Normative level: MUST
- Requirement
- A server that receives a request-target longer than any URI it wishes to parse MUST respond with 414 (URI Too Long).
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- server
- Responsible layer
- Node.js HTTP/1.1 parser and the complete Achieve endpoint
- Implementation evidence
- achieve.js:1407-1441, 1559-1591 (Node HTTP server delegates parsed requests to achieveApp)
- Test evidence
- Raw probes on the final Node.js 24.22.2 Windows and Linux qualification endpoints sent a 20,001-character request-target and received 431; the Windows parser reported HPE_HEADER_OVERFLOW. Earlier Node 22 and standalone controls produced the same status.
- Assessment rationale
- On the qualified Node.js 24.22.2 endpoint, an overlong request-target receives 431 because target and field overflow share the parser's overflow handling. RFC 9112 requires 414 for the demonstrated request-target-length condition.
- Open question
- An upstream Node correction is preferred. Issue nodejs/node#26296 was closed after the generic 431 change in PR #25605, which did not distinguish target overflow.
- V2 traceability
- V2-H105
Conformant Normative level: SHOULD
- Requirement
- A server receiving an invalid request-line SHOULD respond with 400 (Bad Request) unless it redirects with a properly encoded request-target using 301.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- server
- Responsible layer
- Node.js HTTP parser
- Implementation evidence
- achieve.js:1407-1441, 1559-1591 (Node HTTP server delegates parsed requests to achieveApp)
- Test evidence
- Malformed-target coverage exists, but not invalid method-token coverage. Runtime probe: Raw request with method 'GE(T' produced 400 and Connection: close.
- Assessment rationale
- The observed 400 satisfies the ledger expectation and RFC invalid-request-line recommendation.
- Open question
- Ledger wording should cite §3 invalid request-line handling; §3.1 itself defines method as token but does not state this exact SHOULD.
- V2 traceability
- V2-H106
Not applicable Normative level: MUST
- Requirement
- A client MUST generate origin-form when making a request directly to an origin server other than CONNECT or server-wide OPTIONS.
- Conditions
- Client-only generation rule.
- Applicable role
- client
- Responsible layer
- External HTTP client
- Implementation evidence
- Achieve does not generate origin-server requests.
- Test evidence
- Not applicable. Runtime probe: Not run.
- Assessment rationale
- Client request-target generation is outside Achieve’s supported origin-server role.
- Open question
- None.
- V2 traceability
- V2-H107
Conformant Normative level: MUST
- Requirement
- An origin server MUST accept absolute-form in requests to permit transition from proxy use.
- Conditions
- Applies even though clients normally send origin-form directly.
- Applicable role
- origin server
- Responsible layer
- Node.js parser and Achieve request-target logic
- Implementation evidence
- achieve.js:1098-1145, 1407-1433 (Achieve validates parsed request-target and authority)
- Test evidence
- tests/request_target_syntax/verify.js:12-101 (raw HTTP/HTTPS and HTTP/2 target checks; 560 checks) Runtime probe: Raw HTTP/HTTPS absolute-form requests returned 200.
- Assessment rationale
- The endpoint accepts absolute-form and maps its path/query for origin-server processing.
- Open question
- None for tested schemes and forms.
- V2 traceability
- V2-H108
Conformant Normative level: MUST
- Requirement
- When an origin server receives absolute-form, it MUST accept it and use the target authority for request-target reconstruction rather than the Host field.
- Conditions
- Applies to HTTP/1.1 absolute-form requests; proxy generation rules are separate.
- Applicable role
- origin server
- Responsible layer
- Achieve request-target and authority validation
- Implementation evidence
- achieve.js:1117-1145, 1426-1433
- Test evidence
- tests/request_target_syntax/verify.js:12-101 (raw HTTP/HTTPS and HTTP/2 target checks; 560 checks) Runtime probe: Absolute-form requests with a conflicting Host are tested and accepted using target authority.
- Assessment rationale
- Achieve extracts authority from absolute-form and does not use Host as the target authority.
- Open question
- No forwarding/proxy behavior is claimed.
- V2 traceability
- V2-S008
Not applicable Normative level: MUST
- Requirement
- A client MUST send authority-form only for CONNECT requests.
- Conditions
- Client-only generation rule; server validation is separate.
- Applicable role
- client
- Responsible layer
- External HTTP client
- Implementation evidence
- Achieve does not generate CONNECT requests as a client.
- Test evidence
- Not applicable. Runtime probe: Not run.
- Assessment rationale
- This is a client-only generation rule. Achieve’s server-side CONNECT behavior is assessed separately.
- Open question
- None.
- V2 traceability
- V2-H109
Not applicable Normative level: MUST
- Requirement
- A client requesting OPTIONS for the server as a whole MUST send only asterisk-form as the request-target.
- Conditions
- Server-wide OPTIONS and empty-path compatibility conditions.
- Applicable role
- client
- Responsible layer
- External HTTP client
- Implementation evidence
- achieve.js:985-1008, 1107-1109
- Test evidence
- tests/request_target_syntax/verify.js:12-101 (raw HTTP/HTTPS and HTTP/2 target checks; 560 checks); tests/registered_methods/verify.js:117-120 Runtime probe: OPTIONS * is handled with 204; no empty-path compatibility probe was possible from the row as written.
- Assessment rationale
- Client request construction is outside Achieve origin-server responsibility.
- Open question
- None for Achieve origin-server scope.
- V2 traceability
- V2-H110
Not applicable Normative level: MUST
- Requirement
- The last proxy forwarding an absolute-form OPTIONS request whose URI has an empty path and no query MUST send asterisk-form to the origin server.
- Conditions
- Server-wide OPTIONS and empty-path compatibility conditions.
- Applicable role
- final proxy
- Responsible layer
- External final proxy
- Implementation evidence
- achieve.js:985-1008, 1107-1109
- Test evidence
- tests/request_target_syntax/verify.js:12-101 (raw HTTP/HTTPS and HTTP/2 target checks; 560 checks); tests/registered_methods/verify.js:117-120 Runtime probe: OPTIONS * is handled with 204; no empty-path compatibility probe was possible from the row as written.
- Assessment rationale
- Achieve is not an HTTP forwarding proxy; V2 incorrectly assigned this rule to origin-server empty-path processing.
- Open question
- None for Achieve origin-server scope.
- V2 traceability
- V2-H110
Conformant Normative level: MUST
- Requirement
- A server must reject whitespace between a field name and colon with 400.
- 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 parser
- Implementation evidence
- achieve.js:1407-1441, 1559-1591 (Node HTTP server delegates parsed requests to achieveApp)
- Test evidence
- No pre-existing focused assertion. Runtime probe: Raw Host field with whitespace before colon produced 400 and Connection: close.
- Assessment rationale
- The required rejection was observed.
- Open question
- None for the probed runtime.
- V2 traceability
- V2-NEW-037
Conformant Normative level: MUST
- Requirement
- A server receiving obsolete line folding must reject with 400 or replace each fold with SP before interpretation/forwarding.
- 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 parser
- Implementation evidence
- achieve.js:1407-1441, 1559-1591 (Node HTTP server delegates parsed requests to achieveApp)
- Test evidence
- No pre-existing focused assertion. Runtime probe: Raw obs-fold request produced 400 and Connection: close.
- Assessment rationale
- Rejecting obs-fold is one of the permitted required alternatives.
- Open question
- No test of replacement behavior is needed because rejection is sufficient.
- V2 traceability
- V2-NEW-038
Conformant Normative level: MUST
- Requirement
- A recipient of an HTTP/1.0 message containing Transfer-Encoding MUST treat framing as faulty and close the connection after processing.
- Conditions
- Even when Content-Length is also present.
- Applicable role
- recipient
- Responsible layer
- Node.js HTTP parser/socket
- Implementation evidence
- achieve.js:1407-1441, 1559-1591 (Node HTTP server delegates parsed requests to achieveApp)
- Test evidence
- No pre-existing focused HTTP/1.0 Transfer-Encoding assertion. Runtime probe: Raw HTTP/1.0 request with Transfer-Encoding: chunked received a response and the connection closed.
- Assessment rationale
- The endpoint did not reuse the faulty-framed HTTP/1.0 connection; RFC permits processing before closure.
- Open question
- The response was 200; this row requires faulty framing treatment and closure, not a particular status.
- V2 traceability
- V2-H112
Nonconformant Normative level: SHOULD
- Requirement
- A server receiving an unrecognized request transfer coding should respond 501.
- 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 parser/Achieve endpoint
- Implementation evidence
- Node parses Transfer-Encoding before dispatch at achieve.js:1407-1441 and 1559-1591; Achieve has no transfer-coding decoder or registration mechanism.
- Test evidence
- Batch D isolated the final-chunked case with standalone and Achieve controls. Final Node.js 24.22.2 Windows and Linux qualification repeated the unknown-coding request: the endpoint returned 200, removed chunk framing, and delivered the remaining bytes rather than returning 501.
- Assessment rationale
- The final-chunked probe isolates the §6.1 recommendation from §6.3's mandatory final-coding rejection. The qualified endpoint does not understand or decode frobnicate and no documented reason for departing from the 501 SHOULD was identified.
- Open question
- This is a SHOULD-level Node-inherited endpoint defect, not a malformed-final-framing result. Reassess on a newer Node parser or if Achieve gains explicit transfer-coding support.
- V2 traceability
- V2-NEW-040
Conformant Normative level: MAY
- Requirement
- A server MAY reject a request containing both Transfer-Encoding and Content-Length or process Transfer-Encoding alone.
- Conditions
- Both fields are present.
- Applicable role
- server
- Responsible layer
- Node.js HTTP parser/socket
- Implementation evidence
- achieve.js:1407-1441, 1559-1591 (Node HTTP server delegates parsed requests to achieveApp)
- Test evidence
- No focused TE+CL test. Runtime probe: Raw request containing chunked Transfer-Encoding and Content-Length produced 400.
- Assessment rationale
- Rejection is expressly permitted instead of processing Transfer-Encoding alone.
- Open question
- None for the probed runtime.
- V2 traceability
- V2-X037
Conformant Normative level: MUST
- Requirement
- After responding to a request containing both Transfer-Encoding and Content-Length, the server MUST close the connection.
- Conditions
- Both fields are present, regardless of reject/process choice.
- Applicable role
- server
- Responsible layer
- Node.js HTTP parser/socket
- Implementation evidence
- achieve.js:1407-1441, 1559-1591 (Node HTTP server delegates parsed requests to achieveApp)
- Test evidence
- No focused TE+CL closure test. Runtime probe: The TE+CL rejection included Connection: close and the socket ended.
- Assessment rationale
- Mandatory closure after responding was observed.
- Open question
- None for the probed runtime.
- V2 traceability
- V2-X038
Conformant Normative level:
- Requirement
- For a request without Transfer-Encoding or Content-Length, the message body length is zero.
- Conditions
- Applies after all earlier §6.3 framing cases are excluded.
- Applicable role
- server
- Responsible layer
- Node.js HTTP parser
- Implementation evidence
- achieve.js:2480-2540 (POST stream consumption; GET/HEAD dispatch)
- Test evidence
- tests/request_target_syntax/verify.js:12-101 (raw HTTP/HTTPS and HTTP/2 target checks; 560 checks); tests/request_input/verify.js:57-208 (buffered and streamed request input, including abort survival) Runtime probe: Raw GET requests without framing fields were processed as bodyless requests.
- Assessment rationale
- Requests with neither Transfer-Encoding nor Content-Length are delivered with zero-length bodies.
- Open question
- A dedicated assertion of no data events would improve traceability but is not needed to establish observed framing.
- V2 traceability
- V2-H115
Conformant Normative level: MUST
- Requirement
- A request whose final transfer coding is not chunked must receive 400 and connection closure.
- 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 parser/socket
- Implementation evidence
- achieve.js:1407-1441, 1559-1591 (Node HTTP server delegates parsed requests to achieveApp)
- Test evidence
- No focused final-nonchunked test. Runtime probe: Raw request with Transfer-Encoding: unknown (non-chunked final coding) produced 400, Connection: close, and socket end.
- Assessment rationale
- The mandatory status and closure were observed.
- Open question
- The probe also involved an unrecognized coding; a recognized nonfinal coding would isolate this rule further.
- V2 traceability
- V2-NEW-041
Conformant Normative level: MUST
- Requirement
- Invalid or conflicting Content-Length in a request requires 400 and connection closure, except the permitted identical-list normalization.
- 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 parser/socket
- Implementation evidence
- achieve.js:1407-1441, 1559-1591 (Node HTTP server delegates parsed requests to achieveApp)
- Test evidence
- tests/buffered_abort/verify.js:90-260 (incomplete Content-Length/chunked POST aborts) Runtime probe: Conflicting duplicate Content-Length produced 400/close; an identical comma-list was also conservatively rejected with 400/close.
- Assessment rationale
- Invalid/conflicting Content-Length is treated as unrecoverable. The identical-list exception permits successful normalization but does not require it.
- Open question
- A focused accepted identical-list test is unnecessary because rejection remains conservative.
- V2 traceability
- V2-NEW-042
Conformant Normative level: MUST
- Requirement
- A server that receives an incomplete request message MUST close the connection; an incomplete request caused by premature closure MUST be treated as incomplete.
- 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 parser/socket and Achieve buffered-input listeners
- Implementation evidence
- achieve.js:2480-2540 (POST stream consumption; GET/HEAD dispatch)
- Test evidence
- tests/buffered_abort/verify.js:90-260 (incomplete Content-Length/chunked POST aborts); tests/request_input/verify.js:57-208 (buffered and streamed request input, including abort survival) Runtime probe: Existing suites exercise incomplete Content-Length and chunked requests and verify server survival/cleanup.
- Assessment rationale
- Prematurely terminated framed request bodies are not delivered as complete application input and their connections are closed.
- Open question
- The ledger combines sender close and recipient timeout paths; explicit timeout injection is not separately covered.
- V2 traceability
- V2-NEW-043
Conformant Normative level:
- Requirement
- A response to HEAD and any 1xx, 204, or 304 response is terminated by the first empty line and cannot contain a message body.
- Conditions
- Specified request/status cases.
- Applicable role
- recipient/sender
- Responsible layer
- Node.js HTTP sender plus Achieve sendBody/status logic
- Implementation evidence
- achieve.js:944-1044 (GET/POST/HEAD/OPTIONS dispatch and body suppression)
- Test evidence
- tests/response_completion/verify.js:133-279 (HTTP/HTTPS/h2 response completion and HEAD no-body behavior); tests/static_dates/verify.js:75-208 (HEAD/304 no-body and static response framing) Runtime probe: HEAD and 304 responses are verified bodyless across HTTP/HTTPS and HTTP/2.
- Assessment rationale
- The supported HTTP/1.1 endpoint suppresses prohibited bodies for tested HEAD/304 and error paths; Node owns final wire framing.
- Open question
- No Achieve path was found that emits a 1xx response; 204 is exercised by OPTIONS.
- V2 traceability
- V2-X032
Optional not implemented Normative level:
- Requirement
- A successful 2xx CONNECT response switches to tunnel mode immediately after the header section.
- Conditions
- Successful CONNECT.
- Applicable role
- recipient/sender
- Responsible layer
- Achieve/Node CONNECT endpoint
- Implementation evidence
- achieve.js:1255-1342 (explicit CONNECT rejection)
- Test evidence
- tests/connect/verify.js:83-288 (raw CONNECT rejection/closure and HTTP/2 behavior) Runtime probe: Raw CONNECT requests receive non-2xx rejection and closure.
- Assessment rationale
- Achieve does not establish successful CONNECT tunnels, so the conditional 2xx tunnel framing case is absent and permitted.
- Open question
- None unless CONNECT tunneling is added.
- V2 traceability
- V2-X033
Conformant Normative level:
- Requirement
- When Transfer-Encoding ends in chunked, body length is determined by decoding chunks through the terminal chunk.
- Conditions
- Transfer-Encoding final coding is chunked.
- Applicable role
- recipient
- Responsible layer
- Node.js HTTP parser and Achieve request stream
- Implementation evidence
- achieve.js:2480-2540 (POST stream consumption; GET/HEAD dispatch)
- Test evidence
- tests/request_input/verify.js:57-208 (buffered and streamed request input, including abort survival); tests/buffered_abort/verify.js:90-260 (incomplete Content-Length/chunked POST aborts) Runtime probe: Complete chunked inputs are delivered; incomplete terminal-chunk cases abort.
- Assessment rationale
- Observed request-body completion depends on decoding through the terminal chunk.
- Open question
- Large chunk-size overflow limits were not separately assessed because that is a distinct §7.1 requirement absent from this ledger.
- V2 traceability
- V2-X034
Conformant Normative level:
- Requirement
- A valid Content-Length without Transfer-Encoding defines the expected message body length.
- Conditions
- Valid Content-Length and no Transfer-Encoding.
- Applicable role
- recipient
- Responsible layer
- Node.js HTTP parser and Achieve request stream
- Implementation evidence
- achieve.js:2480-2540 (POST stream consumption; GET/HEAD dispatch)
- Test evidence
- tests/request_input/verify.js:57-208 (buffered and streamed request input, including abort survival); tests/buffered_abort/verify.js:90-260 (incomplete Content-Length/chunked POST aborts) Runtime probe: Content-Length input is buffered to end; short bodies abort rather than complete.
- Assessment rationale
- Valid Content-Length controls expected request length, and incomplete bodies are not treated as complete.
- Open question
- None for the exercised buffered paths.
- V2 traceability
- V2-X035
Not applicable Normative level:
- Requirement
- A response with neither Transfer-Encoding nor Content-Length is close-delimited unless an earlier framing case applies.
- Conditions
- Response-only final framing case.
- Applicable role
- response recipient
- Responsible layer
- External HTTP response recipient
- Implementation evidence
- Achieve is the response sender, not a user agent/proxy parsing close-delimited responses.
- Test evidence
- Not applicable. Runtime probe: Not run.
- Assessment rationale
- The row’s response-recipient framing algorithm does not apply to Achieve’s supported origin-server role.
- Open question
- The ledger applicability should not say generally applicable to Achieve HTTP/1.1 without identifying a client role.
- V2 traceability
- V2-X036
Not applicable Normative level: MUST
- Requirement
- If a transfer coding is applied to a request, chunked must be the final coding.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- request sender
- Responsible layer
- External request sender
- Implementation evidence
- Achieve does not originate HTTP requests. Node/application response transfer coding is a different clause.
- Test evidence
- Not applicable. Runtime probe: Not run.
- Assessment rationale
- The recorded obligation explicitly concerns transfer coding applied to a request, while its applicability text incorrectly refers to application-authored responses.
- Open question
- Correct the role/applicability mismatch in the ledger.
- V2 traceability
- V2-NEW-044
Conformant Normative level: MUST NOT
- Requirement
- A sender must not apply chunked more than once.
- 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 response sender
- Implementation evidence
- Node serializes application responses; Achieve does not apply Transfer-Encoding itself.
- Test evidence
- tests/response_completion/verify.js:133-279 (HTTP/HTTPS/h2 response completion and HEAD no-body behavior) Runtime probe: Observed chunked responses have a single Transfer-Encoding layer and parse to completion.
- Assessment rationale
- No Achieve response path applies chunked twice; Node controls serialization.
- Open question
- A byte-level focused test would make the delegation evidence more explicit.
- V2 traceability
- V2-NEW-045
Conformant Normative level: MUST
- Requirement
- A sender using chunked transfer coding MUST generate chunks, the zero-sized terminal chunk, optional permitted trailers, and final CRLF according to the chunked grammar.
- Conditions
- Only when chunked is selected and permitted for the message.
- Applicable role
- sender
- Responsible layer
- Node.js HTTP response sender
- Implementation evidence
- Node serializes chunked output from ServerResponse; Achieve supplies content.
- Test evidence
- tests/response_completion/verify.js:133-279 (HTTP/HTTPS/h2 response completion and HEAD no-body behavior) Runtime probe: HTTP/1.1 streaming/delayed responses parse and terminate successfully.
- Assessment rationale
- Successful parsing to end by Node clients establishes valid terminal framing for exercised chunked responses.
- Open question
- A raw byte grammar assertion would improve but is not necessary for the observed sender behavior.
- V2 traceability
- V2-H116
Conformant Normative level: MUST
- Requirement
- A recipient MUST ignore unrecognized chunk extensions.
- Conditions
- Recipients ought to limit extension length and count to avoid abuse.
- Applicable role
- recipient
- Responsible layer
- Node.js HTTP parser
- Implementation evidence
- Chunk extensions are consumed by Node before Achieve receives body data.
- Test evidence
- Batch D fragmented a chunk-size line across TCP writes and supplied token, quoted-string with escaped quote, valueless, and terminal-chunk extensions. Achieve and standalone Node ignored every extension and delivered exactly DATAXYZ. A chunked request without extensions delivered the DATA control. tests/request_input/verify.js also passed all buffered, streamed, malformed, and aborted-input checks.
- Assessment rationale
- The positive and ordinary controls directly establish that unrecognized valid extensions are ignored without altering decoded content.
- Open question
- The separate ought-to extension-size limit is not part of this MUST record and was not assessed.
- V2 traceability
- V2-H117
Conformant Normative level: MUST NOT
- Requirement
- A recipient MUST NOT merge trailer fields into the header section unless the field definition explicitly permits and defines safe merging.
- Conditions
- Trailer field definitions and RFC 9110 §6.5.1 control permission.
- Applicable role
- recipient
- Responsible layer
- Node.js HTTP parser; application can inspect IncomingMessage trailers
- Implementation evidence
- Achieve passes the Node request object to servlets and does not merge trailers itself.
- Test evidence
- Batch B observed x-batch-trailer only in trailers/rawTrailers over HTTP/1.1 and h2c. Batch D independently sent Authorization in both headers and trailers plus trailer-only X-Trailer: the header retained Basic head, trailers retained Basic tail and tail-value, rawTrailers preserved both lines, and no trailer appeared in headers. Standalone Node matched.
- Assessment rationale
- Direct positive controls establish separate storage of retained non-mergeable trailers; Achieve performs no additional merge.
- Open question
- Bounded to Node.js 22.15.0 and retained trailer fields; discarding a trailer would also be permitted by §7.1.2.
- V2 traceability
- V2-H118
Conformant Normative level: MUST
- Requirement
- A server MUST read the entire request message body or close the connection before reusing it.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- server
- Responsible layer
- Node.js socket/parser plus Achieve input handling
- Implementation evidence
- achieve.js:2480-2540 (POST stream consumption; GET/HEAD dispatch)
- Test evidence
- tests/request_input/verify.js:57-208 (buffered and streamed request input, including abort survival); tests/buffered_abort/verify.js:90-260 (incomplete Content-Length/chunked POST aborts) Runtime probe: Raw GET with Content-Length: 4 followed by a pipelined GET produced two ordered 200 responses; POST paths consume or abort before reuse.
- Assessment rationale
- Observed GET body bytes were framed/consumed before the next request, while POST body listeners consume complete input and aborted bodies close.
- Open question
- Repeat for early servlet responses to unusual methods if registered-method handlers are allowed request bodies.
- V2 traceability
- V2-H119
Conformant Normative level: MUST
- Requirement
- A server receiving pipelined requests MUST send the corresponding responses in the same order the requests were received.
- 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 server/socket
- Implementation evidence
- Node dispatches parsed requests; Achieve responds per request.
- Test evidence
- tests/request_target_syntax/verify.js:12-101 (raw HTTP/HTTPS and HTTP/2 target checks; 560 checks) Runtime probe: Raw pipelined GET /missing then GET /index.html produced responses 404 then 200 in request order.
- Assessment rationale
- The optional permission to process safe requests in parallel was removed from this mandatory ordering record. Existing pipelining evidence establishes response order.
- Open question
- The ledger should split the MAY parallelize clause from the MUST preserve response order clause.
- V2 traceability
- V2-NEW-046
Conformant Normative level: MUST
- Requirement
- A server that receives Connection: close MUST close after its final response.
- Conditions
- Received close option.
- Applicable role
- server
- Responsible layer
- Node.js HTTP server/socket
- Implementation evidence
- achieve.js:1407-1441, 1559-1591 (Node HTTP server delegates parsed requests to achieveApp)
- Test evidence
- Many raw tests send Connection: close. Runtime probe: Raw requests with Connection: close ended after the final response.
- Assessment rationale
- Mandatory connection closure was observed.
- Open question
- None for ordinary completed responses.
- V2 traceability
- V2-X039
Conformant Normative level: SHOULD
- Requirement
- A server that receives Connection: close SHOULD send close in its final response.
- Conditions
- Received close option.
- Applicable role
- server
- Responsible layer
- Node.js HTTP server/socket
- Implementation evidence
- achieve.js:1407-1441, 1559-1591 (Node HTTP server delegates parsed requests to achieveApp)
- Test evidence
- Many raw tests send Connection: close. Runtime probe: Responses to ordinary Connection: close requests included Connection: close.
- Assessment rationale
- The recommended response signal was observed.
- Open question
- The pipelined-close malformed case returned 400/close, also signaling closure.
- V2 traceability
- V2-X040
Conformant Normative level: MUST NOT
- Requirement
- After receiving or sending Connection: close, a server MUST NOT process further requests on that connection.
- Conditions
- Close option received or sent.
- Applicable role
- server
- Responsible layer
- Node.js HTTP server/socket
- Implementation evidence
- achieve.js:1407-1441, 1559-1591 (Node HTTP server delegates parsed requests to achieveApp)
- Test evidence
- No pre-existing pipelined-after-close assertion. Runtime probe: A request containing Connection: close followed by another pipelined request yielded one 400/close response; no second request was processed.
- Assessment rationale
- The server did not process a request following the close signal.
- Open question
- A clean first-response variant could improve diagnostic specificity.
- V2 traceability
- V2-X041
Conformant Normative level: MUST
- Requirement
- A server MUST attempt to initiate an exchange of TLS closure alerts with the client before closing the connection.
- Conditions
- Orderly TLS shutdown is possible.
- Applicable role
- server
- Responsible layer
- Node.js TLS/OpenSSL
- Implementation evidence
- achieve.js:1515-1556 creates https.Server and delegates orderly TLS shutdown to Node/OpenSSL.
- Test evidence
- In Batch D, OpenSSL 3.5.7 requested Connection: close from Achieve HTTPS and captured the server's TLS close notify alert after the complete response; the process exited normally. The same record-level observation succeeded against standalone Node. Existing HTTPS response-completion tests cover application-level completion.
- Assessment rationale
- The TLS record observation directly establishes that the assessed server attempted the required alert exchange before its transport closure. Matching standalone behavior assigns implementation to Node/OpenSSL.
- Open question
- Observed with Node.js 22.15.0 linked to OpenSSL 3.0.16 and an OpenSSL 3.5.7 client on Windows; other runtime/TLS stacks require reassessment.
- V2 traceability
- V2-X042
Conformant Normative level: SHOULD
- Requirement
- A server SHOULD be prepared to receive an incomplete TLS close from the client.
- Conditions
- Client closes without completing the TLS closure-alert exchange.
- Applicable role
- server
- Responsible layer
- Node.js TLS/OpenSSL
- Implementation evidence
- achieve.js:1515-1556 creates https.Server and delegates TLS lifecycle handling to Node/OpenSSL.
- Test evidence
- Batch D completed a keep-alive HTTPS response and then terminated the client without an orderly TLS close in two controls: TLSSocket.destroy and forced termination of an OpenSSL client. Achieve remained operational and a subsequent HTTPS health request returned the complete 200 representation after each abort; standalone Node matched. No uncaught server failure occurred.
- Assessment rationale
- The endpoint tolerated the RFC-described incomplete client close after the client had located the end of server data and continued serving requests, satisfying the SHOULD for the observed configuration.
- Open question
- The probe establishes graceful operational handling, not an exhaustive resource-leak proof under repeated hostile abort load.
- V2 traceability
- V2-X042
Not applicable Normative level: SHOULD
- Requirement
- A client encountering an incomplete TLS close SHOULD treat requests as completed when it received the stated Content-Length or terminal zero-length chunk and SHOULD recover gracefully.
- Conditions
- Client receives an incomplete TLS close after a response with explicit HTTP message framing.
- Applicable role
- client
- Responsible layer
- External HTTPS client
- Implementation evidence
- Achieve is assessed as an origin server and does not implement an HTTPS response client.
- Test evidence
- No runtime probe is needed for the origin-server applicability decision; server-side TLS closure obligations are assessed separately in V3-9112-039 and V3-9112-040.
- Assessment rationale
- The two explicit client SHOULD recommendations are outside Achieve's supported origin-server role.
- Open question
- None for Achieve origin-server scope.
- V2 traceability
- V2-X043
Not applicable Normative level:
- Requirement
- A response with neither chunked transfer coding nor Content-Length is complete only if a valid TLS closure alert has been received.
- Conditions
- Client receives a close-delimited response over TLS.
- Applicable role
- client
- Responsible layer
- External HTTPS client
- Implementation evidence
- Achieve is assessed as an origin server and does not implement an HTTPS response client.
- Test evidence
- No runtime probe is needed for the origin-server applicability decision.
- Assessment rationale
- This declarative completeness rule applies to an HTTP client receiving responses, not the Achieve origin server.
- Open question
- None for Achieve origin-server scope.
- V2 traceability
- V2-X043