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 100 authoritative V3 requirements for RFC 9110. Requirement text is a traceable summary; the linked RFC Editor section supplies the controlling normative text and conditions.
| Classification | Count |
|---|
| Conformant | 83 |
| Nonconformant | 1 |
| Unverified | 5 |
| Not applicable | 8 |
| Optional not implemented | 3 |
| Total | 100 |
|---|
Review the overall findings · Read the methodology · Inspect evidence sources
Unverified Normative level: MUST NOT
- Requirement
- A sender must not generate protocol elements that violate the corresponding ABNF.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- sender/recipient
- Responsible layer
- Shared/Node/Achieve
- Implementation evidence
- Node parses request fields before achieveApp at achieve.js:1407-1441; Achieve additionally validates request-target syntax and authorities before dispatch.
- Test evidence
- tests/request_target_syntax/verify.js exercises malformed targets, but no exhaustive field-parser/size/connection-identity corpus exists.
- Assessment rationale
- The available source and tests do not establish every condition of this obligation; absence of a demonstrated failure is not treated as conformance.
- Open question
- Needs a focused protocol probe or authoritative Node-version evidence covering the exact condition and transport variants.
- V2 traceability
- V2-NEW-001
Unverified Normative level: MUST NOT
- Requirement
- A sender must not generate syntax allowed only for a role it does not have.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- sender/recipient
- Responsible layer
- Shared
- Implementation evidence
- Node parses request fields before achieveApp at achieve.js:1407-1441; Achieve additionally validates request-target syntax and authorities before dispatch.
- Test evidence
- tests/request_target_syntax/verify.js exercises malformed targets, but no exhaustive field-parser/size/connection-identity corpus exists.
- Assessment rationale
- The available source and tests do not establish every condition of this obligation; absence of a demonstrated failure is not treated as conformance.
- Open question
- Needs a focused protocol probe or authoritative Node-version evidence covering the exact condition and transport variants.
- V2 traceability
- V2-NEW-002
Unverified Normative level: SHOULD
- Requirement
- Recipients should parse defensively with only marginal assumptions about conformance and size.
- 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/shared
- Implementation evidence
- Node parses request fields before achieveApp at achieve.js:1407-1441; Achieve additionally validates request-target syntax and authorities before dispatch.
- Test evidence
- tests/request_target_syntax/verify.js exercises malformed targets, but no exhaustive field-parser/size/connection-identity corpus exists.
- Assessment rationale
- The available source and tests do not establish every condition of this obligation; absence of a demonstrated failure is not treated as conformance.
- Open question
- Needs a focused protocol probe or authoritative Node-version evidence covering the exact condition and transport variants.
- V2 traceability
- V2-NEW-003
Unverified Normative level: MUST
- Requirement
- A recipient must accept elements at least as long as values it generates for the same elements.
- 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/shared
- Implementation evidence
- Node parses request fields before achieveApp at achieve.js:1407-1441; Achieve additionally validates request-target syntax and authorities before dispatch.
- Test evidence
- tests/request_target_syntax/verify.js exercises malformed targets, but no exhaustive field-parser/size/connection-identity corpus exists.
- Assessment rationale
- The available source and tests do not establish every condition of this obligation; absence of a demonstrated failure is not treated as conformance.
- Open question
- Needs a focused protocol probe or authoritative Node-version evidence covering the exact condition and transport variants.
- V2 traceability
- V2-NEW-004
Unverified Normative level: MUST
- Requirement
- A recipient must interpret received elements according to defined semantics absent a justified compatibility workaround.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- sender/recipient
- Responsible layer
- Shared
- Implementation evidence
- Node parses request fields before achieveApp at achieve.js:1407-1441; Achieve additionally validates request-target syntax and authorities before dispatch.
- Test evidence
- tests/request_target_syntax/verify.js exercises malformed targets, but no exhaustive field-parser/size/connection-identity corpus exists.
- Assessment rationale
- The available source and tests do not establish every condition of this obligation; absence of a demonstrated failure is not treated as conformance.
- Open question
- Needs a focused protocol probe or authoritative Node-version evidence covering the exact condition and transport variants.
- V2 traceability
- V2-NEW-005
Conformant Normative level: MUST NOT
- Requirement
- A server must not assume two requests on one connection are from the same user agent unless the connection is secured and specific to it.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- server
- Responsible layer
- Achieve request dispatch; Node supplies transport objects
- Implementation evidence
- achieve.js creates a new request Context for each dispatched request and contains no user-agent identity, authentication, or session binding derived from the transport connection.
- Test evidence
- Batch B temporary probe sent two HTTP/1.1 keep-alive requests on one socket with User-Agent values agent-a and agent-b; distinct request contexts reported the current value. Two streams on one h2c session likewise reported distinct request contexts and current values.
- Assessment rationale
- Source and positive controls establish per-request processing without a connection-based user-agent identity assumption. Different HTTP/2 request wrappers are a Node compatibility-API detail, not evidence of identity coupling.
- Open question
- None for Achieve core. Applications that implement authentication remain responsible for their own identity model.
- V2 traceability
- V2-NEW-006
Conformant Normative level: SHOULD
- Requirement
- A non-proxy recipient should ignore unrecognized header and trailer fields unless another rule applies.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- non-proxy recipient (including origin server)
- Responsible layer
- Shared/application
- Implementation evidence
- Node parses request fields before achieveApp at achieve.js:1407-1441; Achieve additionally validates request-target syntax and authorities before dispatch.
- Test evidence
- tests/request_target_syntax/verify.js exercises malformed targets, but no exhaustive field-parser/size/connection-identity corpus exists.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- Evidence is bounded to the supported Node 22 runtime and tested transports.
- V2 traceability
- V2-NEW-007
Conformant Normative level: MUST NOT
- Requirement
- A sender must not generate duplicate field lines unless the field permits list recombination.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- sender
- Responsible layer
- Achieve for core-generated fields; servlet application for application-authored fields; Node serializes
- Implementation evidence
- Core response paths use setHeader/writeHead objects, which replace or uniquely name fields; the only appendHeader use is Vary: Origin, whose definition permits list recombination. Achieve does not synthesize duplicate non-list field lines.
- Test evidence
- Batch B wire captures found no duplicate non-list core fields on representative HTTP/1.1 and h2c static, range, conditional, and error responses. A negative-control servlet deliberately setting an array for X-Non-List produced duplicate HTTP/1.1 lines, confirming that Node does not enforce application semantics.
- Assessment rationale
- Achieve-generated output satisfies the sender obligation. The negative control is application-authored misuse through the general Node response API, not an Achieve-generated protocol defect.
- Open question
- Servlet authors remain responsible for field definitions when deliberately supplying multiple values.
- V2 traceability
- V2-NEW-008
Conformant Normative level: MUST NOT
- Requirement
- A server must not apply a request before receiving the complete header section.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- server
- Responsible layer
- Node/shared
- Implementation evidence
- Node parses request fields before achieveApp at achieve.js:1407-1441; Achieve additionally validates request-target syntax and authorities before dispatch.
- Test evidence
- tests/request_target_syntax/verify.js exercises malformed targets, but no exhaustive field-parser/size/connection-identity corpus exists.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- Evidence is bounded to the supported Node 22 runtime and tested transports.
- V2 traceability
- V2-NEW-009
Conformant Normative level: MAY
- Requirement
- A recipient MAY combine repeated field lines with the same name only without changing message semantics, preserving their order and using comma plus optional whitespace.
- Conditions
- Only fields whose definition permits list recombination; Set-Cookie is a known exception.
- Applicable role
- recipient
- Responsible layer
- Node.js/shared
- Implementation evidence
- Node parses request fields before achieveApp at achieve.js:1407-1441 and exposes normalized and raw field views to Achieve.
- Test evidence
- Batch C raw HTTP/1.1 probes on Node.js 22.15.0 observed ordered comma-SP combination of repeated Accept, semicolon-SP combination of Cookie, retention of the first Authorization value without combination, rejection of duplicate Content-Length with 400, and preservation of all original lines in rawHeaders; standalone Node produced identical results.
- Assessment rationale
- The exercised list, special-case, non-list, and invalid framing controls show that the combinations Node performs preserve the applicable field semantics and order. Achieve does not recombine the lines independently.
- Open question
- Bounded to Node.js 22.15.0 and the field classes exercised; newly defined field semantics remain dependent on Node parser support.
- V2 traceability
- V2-S003
Conformant Normative level: MUST
- Requirement
- A server declining an oversized request field/section must respond with an appropriate 4xx rather than silently ignore it.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- server
- Responsible layer
- Node/shared
- Implementation evidence
- Node parses request fields before achieveApp at achieve.js:1407-1441; parser overflow is handled before Achieve dispatch.
- Test evidence
- Batch C raw HTTP/1.1 probes on Node.js 22.15.0 sent both one 17,000-octet field value and an aggregate section of 180 individually small fields; Achieve and standalone Node returned 431 and closed rather than dispatching with omitted fields. The short-target oversized-field result independently matches rfc9112-h105-investigation.md.
- Assessment rationale
- Both individual-field and aggregate-section refusal conditions produced an appropriate 4xx and no silent omission. The separate overlong request-target 431 defect remains recorded under RFC 9112 and does not invalidate the proper oversized-field result.
- Open question
- Bounded to the tested Node.js 22.15.0 parser configuration.
- V2 traceability
- V2-NEW-010
Conformant Normative level: MUST
- Requirement
- A field parser must exclude permitted leading/trailing whitespace before evaluating the value.
- 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/shared
- Implementation evidence
- Node parses request fields before achieveApp at achieve.js:1407-1441; Achieve additionally validates request-target syntax and authorities before dispatch.
- Test evidence
- tests/request_target_syntax/verify.js exercises malformed targets, but no exhaustive field-parser/size/connection-identity corpus exists.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- Evidence is bounded to the supported Node 22 runtime and tested transports.
- V2 traceability
- V2-NEW-011
Conformant Normative level: MUST
- Requirement
- A recipient of CR, LF, or NUL in a field value must reject the message or replace each with SP before further processing.
- 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
- Implementation evidence
- Node parses request fields before achieveApp at achieve.js:1407-1441; Achieve additionally validates request-target syntax and authorities before dispatch.
- Test evidence
- tests/request_target_syntax/verify.js exercises malformed targets, but no exhaustive field-parser/size/connection-identity corpus exists.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- Evidence is bounded to the supported Node 22 runtime and tested transports.
- V2 traceability
- V2-NEW-012
Conformant Normative level: MUST
- Requirement
- A timestamp parser must accept IMF-fixdate and both obsolete HTTP-date forms.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- HTTP participant
- Responsible layer
- Achieve/Node
- Implementation evidence
- Node parses request fields before achieveApp at achieve.js:1407-1441; Achieve additionally validates request-target syntax and authorities before dispatch.
- Test evidence
- tests/request_target_syntax/verify.js exercises malformed targets, but no exhaustive field-parser/size/connection-identity corpus exists.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- Evidence is bounded to the supported Node 22 runtime and tested transports.
- V2 traceability
- V2-NEW-013
Conformant Normative level: MUST
- Requirement
- A sender must generate HTTP-date timestamps in IMF-fixdate form.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- sender/recipient
- Responsible layer
- Shared
- Implementation evidence
- Node parses request fields before achieveApp at achieve.js:1407-1441; Achieve additionally validates request-target syntax and authorities before dispatch.
- Test evidence
- tests/request_target_syntax/verify.js exercises malformed targets, but no exhaustive field-parser/size/connection-identity corpus exists.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- Evidence is bounded to the supported Node 22 runtime and tested transports.
- V2 traceability
- V2-NEW-014
Conformant Normative level: MUST
- Requirement
- A recipient must interpret an rfc850 two-digit year apparently over 50 years in the future as the most recent matching past year.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- sender/recipient
- Responsible layer
- Achieve/Node
- Implementation evidence
- Node parses request fields before achieveApp at achieve.js:1407-1441; Achieve additionally validates request-target syntax and authorities before dispatch.
- Test evidence
- tests/request_target_syntax/verify.js exercises malformed targets, but no exhaustive field-parser/size/connection-identity corpus exists.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- Evidence is bounded to the supported Node 22 runtime and tested transports.
- V2 traceability
- V2-NEW-015
Conformant Normative level: MUST
- Requirement
- A server MUST send a final response after receiving and interpreting a request unless the connection is closed or an error prevents completion.
- Conditions
- Protocol-specific framing, connection errors, and request aborts can terminate the exchange instead.
- Applicable role
- server
- Responsible layer
- shared
- Implementation evidence
- achieve.js:661-735, achieve.js:1663-1674, and achieve.js:2408-2471 cover normal and exceptional Achieve-managed completion.
- Test evidence
- tests/response_completion/verify.js:133-242, tests/servlet_startup_errors/verify.js, and tests/promise_servlets/verify.js cover completion and failure paths.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- Evidence is bounded to the supported Node 22 runtime and tested transports.
- V2 traceability
- V2-S005
Conformant Normative level: MUST NOT
- Requirement
- A sender must not generate a trailer unless the field definition permits trailers.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- sender
- Responsible layer
- Achieve for core output; servlet application for application-authored trailers
- Implementation evidence
- No Achieve core response path calls addTrailers or sendTrailers; core responses therefore generate no trailer fields. Servlets receive the Node response object and can author trailers independently.
- Test evidence
- Source-wide search found no core trailer-generation call. Batch B ordinary HTTP/1.1 and h2c responses contained no response trailers; request-trailer controls do not change the sender finding.
- Assessment rationale
- Achieve core cannot generate a prohibited trailer because it generates no trailers. A servlet that explicitly adds trailers is responsible for knowing the field definition.
- Open question
- None for Achieve-generated output.
- V2 traceability
- V2-NEW-016
Conformant Normative level: MUST NOT
- Requirement
- A recipient must not merge trailers into headers unless the definition explicitly permits and defines safe merging.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- recipient
- Responsible layer
- Node request parser and compatibility API; Achieve preserves the request object
- Implementation evidence
- Achieve passes Node's request object to each servlet as session.request and does not merge request.trailers into request.headers.
- Test evidence
- Batch B sent X-Batch-Trailer: tail-value after buffered JSON input over chunked HTTP/1.1 and h2c trailing HEADERS. In both protocols the servlet observed the value only in trailers/rawTrailers and not in headers.
- Assessment rationale
- Positive trailer controls directly establish separation from the header section across HTTP/1.1 and HTTP/2.
- Open question
- None for the tested supported transports.
- V2 traceability
- V2-NEW-017
Conformant Normative level: SHOULD NOT
- Requirement
- A server should not put information essential to the user agent only in trailers.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- server
- Responsible layer
- Achieve for core output; servlet application for application-authored trailers
- Implementation evidence
- Achieve core generates no trailers and therefore cannot place information essential to the user agent only in a trailer. Servlet-authored trailer semantics are application responsibility.
- Test evidence
- Source-wide search found no addTrailers/sendTrailers call in Achieve core; representative Batch B responses contained no response trailers.
- Assessment rationale
- The core follows the recommendation by not generating trailers at all. Application-authored content does not establish a core violation.
- Open question
- None for Achieve-generated responses.
- V2 traceability
- V2-NEW-018
Conformant Normative level: MUST
- Requirement
- An HTTP/1.1 origin server receiving no Host field MUST respond 400.
- Conditions
- HTTP/1.1 request lacks Host.
- Applicable role
- origin server
- Responsible layer
- Achieve/Node.js
- Implementation evidence
- achieve.js:1098-1143 and achieve.js:1407-1433 validate request targets/authority before dispatch; Node owns HTTP/1 field parsing.
- Test evidence
- tests/request_target_syntax/verify.js:57-101; all 560 request-target checks passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- Evidence is bounded to the supported Node 22 runtime and tested transports.
- V2 traceability
- V2-X001
Conformant Normative level: MUST
- Requirement
- An HTTP/1.1 origin server receiving more than one Host field MUST respond 400.
- Conditions
- More than one Host field line or combined Host value.
- Applicable role
- origin server
- Responsible layer
- Achieve/Node.js
- Implementation evidence
- achieve.js:1098-1143 and achieve.js:1407-1433 validate request targets/authority before dispatch; Node owns HTTP/1 field parsing.
- Test evidence
- tests/request_target_syntax/verify.js:57-101; all 560 request-target checks passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- Evidence is bounded to the supported Node 22 runtime and tested transports.
- V2 traceability
- V2-X002
Conformant Normative level: MUST
- Requirement
- An HTTP/1.1 origin server receiving an invalid Host field MUST respond 400.
- Conditions
- Host does not conform to authority syntax required for the request.
- Applicable role
- origin server
- Responsible layer
- Achieve/Node.js
- Implementation evidence
- achieve.js:1098-1143 and achieve.js:1407-1433 validate request targets/authority before dispatch; Node owns HTTP/1 field parsing.
- Test evidence
- tests/request_target_syntax/verify.js:57-101; all 560 request-target checks passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- Evidence is bounded to the supported Node 22 runtime and tested transports.
- V2 traceability
- V2-X003
Conformant Normative level: SHOULD
- Requirement
- A sender that generates content SHOULD generate Content-Type unless the intended media type is unknown.
- Conditions
- Exception when the intended media type is unknown.
- Applicable role
- sender
- Responsible layer
- Achieve/application
- Implementation evidence
- achieve.js:1650-1661 maps media types; achieve.js:2057-2070 emits Vary and Content-Encoding; achieve.js:2242-2287 performs content-coding negotiation.
- Test evidence
- tests/compression/verify.js:184-245 and tests/conditional/verify.js:138-155; existing checks cover coding selection, exclusion, Content-Encoding, and Vary.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S011
Conformant Normative level: MUST
- Requirement
- A sender applying a content coding MUST list it in Content-Encoding in application order.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- sender/recipient
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1650-1661 maps media types; achieve.js:2057-2070 emits Vary and Content-Encoding; achieve.js:2242-2287 performs content-coding negotiation.
- Test evidence
- tests/compression/verify.js:184-245 and tests/conditional/verify.js:138-155; existing checks cover coding selection, exclusion, Content-Encoding, and Vary.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S012
Conformant Normative level: MUST NOT
- Requirement
- A server MUST NOT send Content-Length on HEAD unless it equals the octet count that would have been sent for the corresponding GET.
- Conditions
- Conditional permission to send Content-Length on HEAD.
- Applicable role
- server
- Responsible layer
- shared
- Implementation evidence
- achieve.js:970-980 carries a no-body flag for HEAD; achieve.js:1663-1673, achieve.js:2415-2443, and achieve.js:2844-2866 complete responses without bodies where Achieve owns completion; Node enforces protocol framing.
- Test evidence
- tests/response_completion/verify.js:133-242 and tests/static_dates/verify.js:82-98; focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- Evidence is bounded to the supported Node 22 runtime and tested transports.
- V2 traceability
- V2-S015
Conformant Normative level: MUST NOT
- Requirement
- A server MUST NOT send Content-Length on 304 unless it equals the content length of the corresponding 200 response.
- Conditions
- Conditional permission to send Content-Length on 304.
- Applicable role
- server
- Responsible layer
- shared
- Implementation evidence
- achieve.js:970-980 carries a no-body flag for HEAD; achieve.js:1663-1673, achieve.js:2415-2443, and achieve.js:2844-2866 complete responses without bodies where Achieve owns completion; Node enforces protocol framing.
- Test evidence
- tests/response_completion/verify.js:133-242 and tests/static_dates/verify.js:82-98; focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- Evidence is bounded to the supported Node 22 runtime and tested transports.
- V2 traceability
- V2-S016
Conformant Normative level: MUST NOT
- Requirement
- A server MUST NOT send Content-Length in a 1xx response.
- Conditions
- Any informational response.
- Applicable role
- server
- Responsible layer
- Node.js/shared
- Implementation evidence
- achieve.js:970-980 carries a no-body flag for HEAD; achieve.js:1663-1673, achieve.js:2415-2443, and achieve.js:2844-2866 complete responses without bodies where Achieve owns completion; Node enforces protocol framing.
- Test evidence
- tests/response_completion/verify.js:133-242 and tests/static_dates/verify.js:82-98; focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- Evidence is bounded to the supported Node 22 runtime and tested transports.
- V2 traceability
- V2-X004
Conformant Normative level: MUST NOT
- Requirement
- A server MUST NOT send Content-Length in a 204 response.
- Conditions
- Any 204 response.
- Applicable role
- server
- Responsible layer
- Node.js/shared
- Implementation evidence
- achieve.js:970-980 carries a no-body flag for HEAD; achieve.js:1663-1673, achieve.js:2415-2443, and achieve.js:2844-2866 complete responses without bodies where Achieve owns completion; Node enforces protocol framing.
- Test evidence
- tests/response_completion/verify.js:133-242 and tests/static_dates/verify.js:82-98; focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- Evidence is bounded to the supported Node 22 runtime and tested transports.
- V2 traceability
- V2-X005
Optional not implemented Normative level: MUST NOT
- Requirement
- A server MUST NOT send Content-Length in a successful 2xx response to CONNECT.
- Conditions
- Successful CONNECT only.
- Applicable role
- server
- Responsible layer
- Node.js/shared
- Implementation evidence
- achieve.js:1052-1073 and achieve.js:1267-1342 validate authority-form CONNECT and implement only rejection/error responses, not successful tunneling.
- Test evidence
- tests/connect/verify.js:140-288; focused CONNECT suite passed during this assessment.
- Assessment rationale
- The referenced capability is optional and Achieve does not implement the triggering successful/optional behavior.
- Open question
- None recorded.
- V2 traceability
- V2-X006
Conformant Normative level:
- Requirement
- A strong validator changes whenever representation data observable in a 200 response changes.
- Conditions
- This is the defining property of a strong validator, not an explicit BCP 14 keyword.
- Applicable role
- origin server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1711-1720 constructs representation-specific strong tags; achieve.js:1770-1807 generates/clamps dates and parses all three HTTP-date forms; achieve.js:2077-2126 uses the opened representation metadata.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S017
Conformant Normative level:
- Requirement
- A validator shared by representations with different representation data is weak; content-coded and identity data therefore require distinct strong validators when their bytes differ.
- Conditions
- Representations may share a strong validator only when their representation data are identical.
- Applicable role
- origin server
- Responsible layer
- Achieve/application
- Implementation evidence
- achieve.js:1711-1720 constructs representation-specific strong tags; achieve.js:1770-1807 generates/clamps dates and parses all three HTTP-date forms; achieve.js:2077-2126 uses the opened representation metadata.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S023
Conformant Normative level: SHOULD
- Requirement
- The origin server should obtain Last-Modified as close as possible to Date generation.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- origin server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1711-1720 constructs representation-specific strong tags; achieve.js:1770-1807 generates/clamps dates and parses all three HTTP-date forms; achieve.js:2077-2126 uses the opened representation metadata.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-NEW-019
Conformant Normative level: MUST
- Requirement
- A future implementation-derived Last-Modified value must be replaced with message origination Date.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- HTTP participant
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1711-1720 constructs representation-specific strong tags; achieve.js:1770-1807 generates/clamps dates and parses all three HTTP-date forms; achieve.js:2077-2126 uses the opened representation metadata.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-NEW-020
Conformant Normative level: SHOULD
- Requirement
- An origin server SHOULD send Last-Modified when a modification date can be reasonably and consistently determined.
- Conditions
- Only for selected representations with a reasonably and consistently determinable modification date.
- Applicable role
- origin server
- Responsible layer
- Achieve/application
- Implementation evidence
- achieve.js:1711-1720 constructs representation-specific strong tags; achieve.js:1770-1807 generates/clamps dates and parses all three HTTP-date forms; achieve.js:2077-2126 uses the opened representation metadata.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S019
Conformant Normative level: SHOULD
- Requirement
- An origin server should send ETag where changes can be reasonably and consistently detected.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- origin server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1711-1720 constructs representation-specific strong tags; achieve.js:1770-1807 generates/clamps dates and parses all three HTTP-date forms; achieve.js:2077-2126 uses the opened representation metadata.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-NEW-021
Conformant Normative level:
- Requirement
- An entity tag has the grammar entity-tag = [ weak ] opaque-tag, with opaque-tag enclosed in DQUOTE.
- Conditions
- Senders must generate grammar-conforming entity tags.
- Applicable role
- sender
- Responsible layer
- Achieve/application
- Implementation evidence
- achieve.js:1711-1720 constructs representation-specific strong tags; achieve.js:1770-1807 generates/clamps dates and parses all three HTTP-date forms; achieve.js:2077-2126 uses the opened representation metadata.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S021
Conformant Normative level: MUST
- Requirement
- A validator that is not strong MUST be marked weak with W/.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- HTTP participant
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1711-1720 constructs representation-specific strong tags; achieve.js:1770-1807 generates/clamps dates and parses all three HTTP-date forms; achieve.js:2077-2126 uses the opened representation metadata.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S022
Conformant Normative level: MUST
- Requirement
- All general-purpose origin servers MUST support GET and HEAD.
- Conditions
- Applies to general-purpose origin servers.
- Applicable role
- origin server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:944-980 and achieve.js:1011-1049 provide GET and HEAD dispatch paths.
- Test evidence
- tests/response_completion/verify.js:133-242 and tests/request_methods/verify.js provide GET/HEAD request coverage.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S026
Not applicable Normative level: SHOULD NOT
- Requirement
- A client SHOULD NOT automatically retry a non-idempotent request without knowing it was not applied.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- client
- Responsible layer
- Achieve
- Implementation evidence
- Relevant request dispatch and response handling are in achieve.js:944-1049 and achieve.js:1407-1441; no more specific core enforcement was identified.
- Test evidence
- No focused test establishing this complete obligation was identified.
- Assessment rationale
- The obligation is conditional on a role, status, or feature that Achieve core does not exercise in its supported origin-server behavior.
- Open question
- None recorded.
- V2 traceability
- V2-S024
Conformant Normative level: MUST NOT
- Requirement
- A server MUST NOT send content in a HEAD response.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- server
- Responsible layer
- Shared
- Implementation evidence
- achieve.js:970-980 carries a no-body flag for HEAD; achieve.js:1663-1673, achieve.js:2415-2443, and achieve.js:2844-2866 complete responses without bodies where Achieve owns completion; Node enforces protocol framing.
- Test evidence
- tests/response_completion/verify.js:133-242 and tests/static_dates/verify.js:82-98; focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- Evidence is bounded to the supported Node 22 runtime and tested transports.
- V2 traceability
- V2-S027
Conformant Normative level: SHOULD
- Requirement
- HEAD SHOULD send the same header fields as GET except fields determined only while generating content.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- HTTP participant
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:970-980 carries a no-body flag for HEAD; achieve.js:1663-1673, achieve.js:2415-2443, and achieve.js:2844-2866 complete responses without bodies where Achieve owns completion; Node enforces protocol framing.
- Test evidence
- tests/response_completion/verify.js:133-242 and tests/static_dates/verify.js:82-98; focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S028
Conformant Normative level: MUST
- Requirement
- A server MUST reject a CONNECT request whose target is not valid authority-form, including an empty or invalid port, with 400.
- Conditions
- Classic CONNECT; extended CONNECT has separate HTTP/2 rules.
- Applicable role
- server
- Responsible layer
- Achieve/Node.js
- Implementation evidence
- achieve.js:1052-1073 and achieve.js:1267-1342 validate authority-form CONNECT and implement only rejection/error responses, not successful tunneling.
- Test evidence
- tests/connect/verify.js:140-288; focused CONNECT suite passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- Evidence is bounded to the supported Node 22 runtime and tested transports.
- V2 traceability
- V2-S030
Optional not implemented Normative level: MUST NOT
- Requirement
- A server MUST NOT send Transfer-Encoding or Content-Length in a successful 2xx CONNECT response.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1052-1073 and achieve.js:1267-1342 validate authority-form CONNECT and implement only rejection/error responses, not successful tunneling.
- Test evidence
- tests/connect/verify.js:140-288; focused CONNECT suite passed during this assessment.
- Assessment rationale
- The referenced capability is optional and Achieve does not implement the triggering successful/optional behavior.
- Open question
- None recorded.
- V2 traceability
- V2-S031
Not applicable Normative level: MUST NOT
- Requirement
- A client MUST NOT send content in TRACE.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- client
- Responsible layer
- Achieve
- Implementation evidence
- Relevant request dispatch and response handling are in achieve.js:944-1049 and achieve.js:1407-1441; no more specific core enforcement was identified.
- Test evidence
- No focused test establishing this complete obligation was identified.
- Assessment rationale
- The obligation is conditional on a role, status, or feature that Achieve core does not exercise in its supported origin-server behavior.
- Open question
- None recorded.
- V2 traceability
- V2-S032
Conformant Normative level: MUST
- Requirement
- For a qualifying HTTP/1.1 100-continue request, an origin server must send either 100 Continue or a final response.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- origin server
- Responsible layer
- Node/shared
- Implementation evidence
- Achieve creates Node HTTP/1.1 servers with a request listener at achieve.js:1559-1591 and installs no checkContinue or checkExpectation override, so Node owns the interim/default expectation boundary.
- Test evidence
- A Batch C raw TCP probe withheld the four-octet request content after complete qualifying HTTP/1.1 headers and observed an exact HTTP/1.1 100 Continue response, followed by 200 after content delivery. Unsupported Expect produced final 417; an HTTP/1.0 control emitted no 100. Standalone Node matched Achieve.
- Assessment rationale
- The qualifying request received one of the two required immediate alternatives. Positive and negative controls establish that the result was expectation processing rather than an ordinary response artifact.
- Open question
- Bounded to the tested Node.js 22.15.0 HTTP/1.1 endpoint.
- V2 traceability
- V2-NEW-022
Conformant Normative level: MUST NOT
- Requirement
- The origin server must not wait for request content before sending the 100 response.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- origin server
- Responsible layer
- Node/shared
- Implementation evidence
- Achieve creates Node HTTP/1.1 servers with a request listener at achieve.js:1559-1591 and installs no checkContinue override.
- Test evidence
- The Batch C raw TCP client sent complete qualifying headers but withheld all request content. Achieve returned the complete 100 Continue response in 1 ms; only then did the probe transmit DATA and receive final 200. Standalone Node behaved identically.
- Assessment rationale
- The wire ordering directly establishes that the endpoint did not wait for request content before sending 100 Continue.
- Open question
- Timing is an observed local bound, not a universal latency guarantee; the protocol ordering is the material evidence.
- V2 traceability
- V2-NEW-023
Conformant Normative level: MUST
- Requirement
- An origin server with a clock MUST generate Date in 2xx responses.
- Conditions
- Origin server has a clock.
- Applicable role
- origin server
- Responsible layer
- Node.js/shared
- Implementation evidence
- achieve.js:1770-1777 explicitly sets Date for filesystem responses; other response Date generation is delegated to Node HTTP servers created at achieve.js:1463-1512 and achieve.js:1515-1591.
- Test evidence
- tests/static_dates/verify.js:82-108 verifies Date for static successes; no focused all-status/no-clock matrix exists.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- Evidence is bounded to the supported Node 22 runtime and tested transports.
- V2 traceability
- V2-X007
Conformant Normative level: MUST
- Requirement
- An origin server with a clock MUST generate Date in 3xx responses.
- Conditions
- Origin server has a clock.
- Applicable role
- origin server
- Responsible layer
- Node.js/shared
- Implementation evidence
- achieve.js:1770-1777 explicitly sets Date for filesystem responses; other response Date generation is delegated to Node HTTP servers created at achieve.js:1463-1512 and achieve.js:1515-1591.
- Test evidence
- tests/static_dates/verify.js:82-108 verifies Date for static successes; no focused all-status/no-clock matrix exists.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- Evidence is bounded to the supported Node 22 runtime and tested transports.
- V2 traceability
- V2-X008
Conformant Normative level: MUST
- Requirement
- An origin server with a clock MUST generate Date in 4xx responses.
- Conditions
- Origin server has a clock.
- Applicable role
- origin server
- Responsible layer
- Node.js/shared
- Implementation evidence
- achieve.js:1770-1777 explicitly sets Date for filesystem responses; other response Date generation is delegated to Node HTTP servers created at achieve.js:1463-1512 and achieve.js:1515-1591.
- Test evidence
- tests/static_dates/verify.js:82-108 verifies Date for static successes; no focused all-status/no-clock matrix exists.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- Evidence is bounded to the supported Node 22 runtime and tested transports.
- V2 traceability
- V2-X009
Not applicable Normative level: MUST NOT
- Requirement
- An origin server without a clock MUST NOT generate Date.
- Conditions
- Origin server lacks a clock.
- Applicable role
- origin server
- Responsible layer
- Node.js/shared
- Implementation evidence
- The assessed Achieve 3.0.6 endpoint runs on Node.js 22.15.0 with a usable system clock; achieve.js:1768-1777 uses that clock for static-response Date and Node generates Date on other ordinary HTTP responses.
- Test evidence
- tests/static_dates/verify.js:82-108 validates clock-backed Date behavior. The Batch C environment had a functioning clock; no representative clockless Node configuration exists in the supported endpoint.
- Assessment rationale
- The RFC prohibition is conditional on the origin server lacking a clock. That condition is false for the assessed configuration, so ordinary Date generation neither exercises nor violates this requirement.
- Open question
- Reassess only if Achieve supports an environment in which Node has no usable clock; replacing Date in a test would not establish such a platform condition.
- V2 traceability
- V2-X010
Not applicable Normative level: MUST
- Requirement
- A server generating a 401 response MUST send at least one WWW-Authenticate challenge.
- Conditions
- Every generated 401 response.
- Applicable role
- server
- Responsible layer
- Servlet application when it selects 401; Achieve core does not generate 401
- Implementation evidence
- No Achieve core response path selects status 401. Servlets receive the Node response object and are responsible for pairing an application-selected 401 with an applicable WWW-Authenticate challenge.
- Test evidence
- Source search found no core 401 generation or authentication challenge path. No artificial servlet omission is treated as an Achieve-core failure.
- Assessment rationale
- The conditional obligation is not reached by Achieve core. It applies to an application that chooses to generate a 401 response.
- Open question
- None for Achieve core; application conformance depends on the deployed servlet.
- V2 traceability
- V2-S036
Conformant Normative level: SHOULD
- Requirement
- If no acceptable coding is available, the origin server should send identity unless identity is unacceptable.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- origin server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1650-1661 maps media types; achieve.js:2057-2070 emits Vary and Content-Encoding; achieve.js:2242-2287 performs content-coding negotiation.
- Test evidence
- tests/compression/verify.js:184-245 and tests/conditional/verify.js:138-155; existing checks cover coding selection, exclusion, Content-Encoding, and Vary.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-NEW-024
Conformant Normative level: SHOULD
- Requirement
- An origin server SHOULD generate Vary on a cacheable response intended for selective reuse based on request fields.
- Conditions
- When selective reuse depends on request fields; omission can be intentional when revalidation is always desired.
- Applicable role
- origin server
- Responsible layer
- Achieve/application
- Implementation evidence
- achieve.js:1650-1661 maps media types; achieve.js:2057-2070 emits Vary and Content-Encoding; achieve.js:2242-2287 performs content-coding negotiation.
- Test evidence
- tests/compression/verify.js:184-245 and tests/conditional/verify.js:138-155; existing checks cover coding selection, exclusion, Content-Encoding, and Vary.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S037
Not applicable Normative level: MUST NOT
- Requirement
- A proxy MUST NOT generate Vary with the value "*".
- Conditions
- Proxy-only generation rule.
- Applicable role
- proxy
- Responsible layer
- external
- Implementation evidence
- achieve.js:573 appends Vary for origin-sensitive CORS and achieve.js:2057 emits Vary: Accept-Encoding for negotiated static representations.
- Test evidence
- No focused test establishing this complete obligation was identified.
- Assessment rationale
- The obligation is conditional on a role, status, or feature that Achieve core does not exercise in its supported origin-server behavior.
- Open question
- None recorded.
- V2 traceability
- V2-S038
Conformant Normative level: MUST
- Requirement
- An origin server receiving If-Match MUST evaluate it before performing the method.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- origin server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1705-1766 parses/compares entity tags; achieve.js:1809-1855 evaluates preconditions; achieve.js:3100-3139 evaluates If-Range and Range for media.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S039
Conformant Normative level: MUST
- Requirement
- If If-Match evaluates false, the origin server MUST NOT perform the requested method.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- origin server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1705-1766 parses/compares entity tags; achieve.js:1809-1855 evaluates preconditions; achieve.js:3100-3139 evaluates If-Range and Range for media.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S040
Conformant Normative level: MUST
- Requirement
- An origin server receiving If-None-Match MUST evaluate it before performing the method.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- origin server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1705-1766 parses/compares entity tags; achieve.js:1809-1855 evaluates preconditions; achieve.js:3100-3139 evaluates If-Range and Range for media.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S041
Conformant Normative level: MUST
- Requirement
- False If-None-Match MUST produce 304 for GET/HEAD or 412 for other methods.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- HTTP participant
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1705-1766 parses/compares entity tags; achieve.js:1809-1855 evaluates preconditions; achieve.js:3100-3139 evaluates If-Range and Range for media.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S042
Conformant Normative level: MUST
- Requirement
- An origin server MUST ignore If-Modified-Since when If-None-Match is present.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- origin server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1705-1766 parses/compares entity tags; achieve.js:1809-1855 evaluates preconditions; achieve.js:3100-3139 evaluates If-Range and Range for media.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S043
Conformant Normative level: MUST
- Requirement
- A recipient MUST ignore If-Modified-Since when If-None-Match is present.
- Conditions
- Both fields present.
- Applicable role
- origin server/cache
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1705-1766 parses/compares entity tags; achieve.js:1809-1855 evaluates preconditions; achieve.js:3100-3139 evaluates If-Range and Range for media.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-X011
Conformant Normative level: MUST
- Requirement
- A recipient MUST ignore If-Modified-Since when the value is invalid or has more than one member.
- Conditions
- Invalid/list date.
- Applicable role
- origin server/cache
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1705-1766 parses/compares entity tags; achieve.js:1809-1855 evaluates preconditions; achieve.js:3100-3139 evaluates If-Range and Range for media.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-X012
Conformant Normative level: MUST
- Requirement
- A recipient MUST ignore If-Modified-Since for methods other than GET and HEAD.
- Conditions
- Non-GET/HEAD request.
- Applicable role
- origin server/cache
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1705-1766 parses/compares entity tags; achieve.js:1809-1855 evaluates preconditions; achieve.js:3100-3139 evaluates If-Range and Range for media.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-X013
Conformant Normative level: MUST
- Requirement
- A recipient MUST ignore If-Modified-Since when no modification date is available.
- Conditions
- Selected representation lacks modification date.
- Applicable role
- origin server/cache
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1705-1766 parses/compares entity tags; achieve.js:1809-1855 evaluates preconditions; achieve.js:3100-3139 evaluates If-Range and Range for media.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-X014
Conformant Normative level: SHOULD
- Requirement
- An origin server SHOULD evaluate a valid applicable If-Modified-Since before performing the method.
- Conditions
- No If-None-Match; request selects representation.
- Applicable role
- origin server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1705-1766 parses/compares entity tags; achieve.js:1809-1855 evaluates preconditions; achieve.js:3100-3139 evaluates If-Range and Range for media.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-X015
Conformant Normative level: SHOULD NOT
- Requirement
- When evaluated If-Modified-Since is false, the origin server SHOULD NOT perform the method.
- Conditions
- Condition evaluates false.
- Applicable role
- origin server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1705-1766 parses/compares entity tags; achieve.js:1809-1855 evaluates preconditions; achieve.js:3100-3139 evaluates If-Range and Range for media.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-X016
Conformant Normative level: SHOULD
- Requirement
- When evaluated If-Modified-Since is false, the origin server SHOULD generate 304 with useful cache metadata.
- Conditions
- GET or HEAD condition evaluates false.
- Applicable role
- origin server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1705-1766 parses/compares entity tags; achieve.js:1809-1855 evaluates preconditions; achieve.js:3100-3139 evaluates If-Range and Range for media.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-X017
Conformant Normative level: MUST
- Requirement
- If valid If-Unmodified-Since is false, the origin server MUST NOT perform the method.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- origin server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1705-1766 parses/compares entity tags; achieve.js:1809-1855 evaluates preconditions; achieve.js:3100-3139 evaluates If-Range and Range for media.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S047
Conformant Normative level: MUST
- Requirement
- A recipient MUST ignore If-Unmodified-Since when If-Match is present.
- Conditions
- Both fields present.
- Applicable role
- origin server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1705-1766 parses/compares entity tags; achieve.js:1809-1855 evaluates preconditions; achieve.js:3100-3139 evaluates If-Range and Range for media.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-X018
Conformant Normative level: MUST
- Requirement
- A recipient MUST ignore If-Unmodified-Since when its value is invalid or appears to be a list.
- Conditions
- Invalid/list date.
- Applicable role
- origin server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1705-1766 parses/compares entity tags; achieve.js:1809-1855 evaluates preconditions; achieve.js:3100-3139 evaluates If-Range and Range for media.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-X019
Conformant Normative level: MUST
- Requirement
- A recipient MUST ignore If-Unmodified-Since when no modification date is available.
- Conditions
- Selected representation lacks modification date.
- Applicable role
- origin server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1705-1766 parses/compares entity tags; achieve.js:1809-1855 evaluates preconditions; achieve.js:3100-3139 evaluates If-Range and Range for media.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-X020
Conformant Normative level: MUST
- Requirement
- An origin server receiving If-Range on a Range request MUST evaluate it before performing the method.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- origin server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1705-1766 parses/compares entity tags; achieve.js:1809-1855 evaluates preconditions; achieve.js:3100-3139 evaluates If-Range and Range for media.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S048
Conformant Normative level:
- Requirement
- During mandatory If-Range evaluation, a date-form condition is true only when the date is a strong validator under §8.8.2.2 and exactly matches Last-Modified.
- Conditions
- A non-strong date or any non-exact match is false.
- Applicable role
- origin server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1705-1766 parses/compares entity tags; achieve.js:1809-1855 evaluates preconditions; achieve.js:3100-3139 evaluates If-Range and Range for media.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S049
Conformant Normative level: MUST
- Requirement
- A recipient MUST ignore Range when If-Range evaluates false.
- Conditions
- If-Range false.
- Applicable role
- origin server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1705-1766 parses/compares entity tags; achieve.js:1809-1855 evaluates preconditions; achieve.js:3100-3139 evaluates If-Range and Range for media.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-X021
Conformant Normative level: SHOULD
- Requirement
- A recipient SHOULD process Range when If-Range evaluates true.
- Conditions
- If-Range true.
- Applicable role
- origin server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1705-1766 parses/compares entity tags; achieve.js:1809-1855 evaluates preconditions; achieve.js:3100-3139 evaluates If-Range and Range for media.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-X022
Conformant Normative level: MUST
- Requirement
- A recipient MUST ignore preconditions when the normal response would not be 2xx or 412.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- sender/recipient
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1705-1766 parses/compares entity tags; achieve.js:1809-1855 evaluates preconditions; achieve.js:3100-3139 evaluates If-Range and Range for media.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S051
Conformant Normative level: MUST
- Requirement
- A server MUST ignore conditional fields for methods whose selection is not conditional, including CONNECT, OPTIONS, and TRACE.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1705-1766 parses/compares entity tags; achieve.js:1809-1855 evaluates preconditions; achieve.js:3100-3139 evaluates If-Range and Range for media.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S052
Conformant Normative level: MUST
- Requirement
- Preconditions MUST be evaluated in the specified order: If-Match, If-Unmodified-Since, If-None-Match, If-Modified-Since, then If-Range.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- HTTP participant
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:1705-1766 parses/compares entity tags; achieve.js:1809-1855 evaluates preconditions; achieve.js:3100-3139 evaluates If-Range and Range for media.
- Test evidence
- tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S053
Conformant Normative level: MUST
- Requirement
- A server MUST ignore a Range field with an unknown range unit.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:3008-3087 parses byte ranges; achieve.js:3132-3204 selects full/206/400/416 behavior and emits Content-Range and lengths.
- Test evidence
- tests/byte_ranges/verify.js:92-143 and tests/conditional/verify.js:223-248; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S054
Conformant Normative level: MUST
- Requirement
- A server MUST ignore Range on a request method for which range handling is not defined.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:3008-3087 parses byte ranges; achieve.js:3132-3204 selects full/206/400/416 behavior and emits Content-Range and lengths.
- Test evidence
- tests/byte_ranges/verify.js:92-143 and tests/conditional/verify.js:223-248; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S055
Conformant Normative level: SHOULD
- Requirement
- An origin server that supports a range unit SHOULD send 206 for a satisfiable Range request.
- Conditions
- Applicable Range request is satisfiable.
- Applicable role
- origin server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:3008-3087 parses byte ranges; achieve.js:3132-3204 selects full/206/400/416 behavior and emits Content-Range and lengths.
- Test evidence
- tests/byte_ranges/verify.js:92-143 and tests/conditional/verify.js:223-248; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-X023
Conformant Normative level: SHOULD
- Requirement
- An origin server SHOULD send 416 for an unsatisfiable applicable Range request.
- Conditions
- No requested range is satisfiable.
- Applicable role
- origin server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:3008-3087 parses byte ranges; achieve.js:3132-3204 selects full/206/400/416 behavior and emits Content-Range and lengths.
- Test evidence
- tests/byte_ranges/verify.js:92-143 and tests/conditional/verify.js:223-248; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-X024
Conformant Normative level: MAY
- Requirement
- A server MAY ignore or reject a Range field containing invalid range syntax.
- Conditions
- Invalid range-set syntax.
- Applicable role
- origin server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:3008-3087 parses byte ranges; achieve.js:3132-3204 selects full/206/400/416 behavior and emits Content-Range and lengths.
- Test evidence
- tests/byte_ranges/verify.js:92-143 and tests/conditional/verify.js:223-248; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-X025
Conformant Normative level: MAY
- Requirement
- A server MAY ignore or reject a Range request containing excessive or overlapping ranges indicating abuse.
- Conditions
- Potential denial-of-service range set.
- Applicable role
- origin server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:3008-3087 parses byte ranges; achieve.js:3132-3204 selects full/206/400/416 behavior and emits Content-Range and lengths.
- Test evidence
- tests/byte_ranges/verify.js:92-143 and tests/conditional/verify.js:223-248; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-X026
Conformant Normative level: SHOULD
- Requirement
- A 416 response to a byte-range request SHOULD send Content-Range with the current complete length.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- HTTP participant
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:3008-3087 parses byte ranges; achieve.js:3132-3204 selects full/206/400/416 behavior and emits Content-Range and lengths.
- Test evidence
- tests/byte_ranges/verify.js:92-143 and tests/conditional/verify.js:223-248; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S058
Conformant Normative level: MUST NOT
- Requirement
- A server must not generate content in a 205 response.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- server
- Responsible layer
- Achieve servlet response boundary and Node.js HTTP serializers
- Implementation evidence
- achieve.js invokeServlet wraps the exposed response write, end, writeHead, and flushHeaders paths. For status 205 it removes Transfer-Encoding, sets Content-Length to 0, replaces supported content with an empty value, and still invokes Node's native methods. Unsupported chunks pass unchanged to Node for validation.
- Test evidence
- tests/response_completion/verify.js exercises managed string, Buffer, Uint8Array, and Promise results; application-owned write/end/writeHead/flushHeaders; invalid chunks; writes after end and destruction; callback ordering; header overloads; and connection reuse over HTTP, HTTPS, h2c, and secure HTTP/2. The focused verifier and all 37 aggregate suites pass on Node.js 22.15.0.
- Assessment rationale
- All supported tested servlet response paths preserve status 205 while transmitting no content, no Transfer-Encoding, and Content-Length 0. Native validation, lifecycle errors, callback results, and transport distinctions are preserved by invoking the original Node response methods.
- Open question
- Lower-level direct socket or HTTP/2 stream manipulation is outside the supported servlet response API and was not treated as an application response path.
- V2 traceability
- V2-NEW-030
Conformant Normative level: MUST
- Requirement
- A 206 sender must include Date, Cache-Control, ETag, Expires, Content-Location, and Vary when each would appear on the corresponding 200.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- sender/recipient
- Responsible layer
- Achieve static/media response generation; Node serializes
- Implementation evidence
- The static/media path sets Date and ETag before range selection and applies the same relevant metadata to 200 and 206 responses; fields not generated on 200 are not conditionally required on 206.
- Test evidence
- Batch B paired 200 and ordinary/If-Range 206 responses over HTTP/1.1 and h2c. Date and ETag appeared on all; Cache-Control, Expires, Content-Location, and Vary were absent from both corresponding 200 and 206 responses.
- Assessment rationale
- Every field in the section 15.3.7 mandatory list that appeared on the corresponding 200 also appeared on each 206 in both tested protocols.
- Open question
- None for the tested static identity representation.
- V2 traceability
- V2-NEW-025
Conformant Normative level: SHOULD NOT
- Requirement
- For 206 responding to If-Range, the sender should not repeat unnecessary representation fields beyond the required set.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- sender/recipient
- Responsible layer
- Achieve static/media response generation
- Implementation evidence
- After If-Range evaluation and range parsing, the media response path identifies the successful If-Range single-part 206 case, omits Content-Type, and skips Last-Modified while retaining Date, ETag, Content-Range, partial Content-Length, Accept-Ranges, and Server. Ordinary 206 and false-condition 200 paths retain their normal metadata.
- Test evidence
- The byte_ranges verifier checks matching strong If-Range, ordinary Range, nonmatching entity-tag, and conservative date-form cases over HTTP, HTTPS, h2c, and secure HTTP/2. It verifies exact partial bytes, current ETag, Content-Range, partial Content-Length, required metadata retention, and Content-Type/Last-Modified omission only on the successful If-Range 206 path.
- Assessment rationale
- The localized field selection follows the section 15.3.7 SHOULD NOT recommendation without changing validators, range bytes, framing, file I/O, ordinary 206 responses, or full 200 responses.
- Open question
- Date-form If-Range remains conservatively false because no strong date validator is established in the current resource model; the successful-response condition also covers a future supported match.
- V2 traceability
- V2-NEW-026
Conformant Normative level: MUST
- Requirement
- Otherwise, a 206 sender must include all representation fields that the corresponding 200 would send.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- sender/recipient
- Responsible layer
- Achieve static/media response generation
- Implementation evidence
- Ordinary range responses use the same representation-selection metadata as the corresponding full response while adjusting message length and adding Content-Range.
- Test evidence
- Batch B ordinary 206 responses over HTTP/1.1 and h2c retained the corresponding 200 ETag, Last-Modified, and Content-Type; Date was also present. No Content-Encoding, Content-Location, or Vary appeared on either response.
- Assessment rationale
- All representation fields actually sent on the corresponding 200 were present on the non-If-Range 206. Message-specific Content-Length and Content-Range differences are expected.
- Open question
- None for the tested static identity representation.
- V2 traceability
- V2-NEW-027
Conformant Normative level: MUST
- Requirement
- A single-part 206 response MUST generate Content-Range describing the enclosed selected range.
- Conditions
- One selected range is transferred.
- Applicable role
- server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:3008-3087 parses byte ranges; achieve.js:3132-3204 selects full/206/400/416 behavior and emits Content-Range and lengths.
- Test evidence
- tests/byte_ranges/verify.js:92-143 and tests/conditional/verify.js:223-248; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-X027
Conformant Normative level:
- Requirement
- The content of a single-part 206 response consists of the representation data for the range identified by Content-Range.
- Conditions
- One selected range is transferred.
- Applicable role
- server
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:3008-3087 parses byte ranges; achieve.js:3132-3204 selects full/206/400/416 behavior and emits Content-Range and lengths.
- Test evidence
- tests/byte_ranges/verify.js:92-143 and tests/conditional/verify.js:223-248; both focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-X028
Not applicable Normative level: MUST
- Requirement
- If a 206 transfers multiple parts, the sender MUST use multipart/byteranges.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- sender/recipient
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:3008-3087 parses byte ranges; achieve.js:3132-3204 selects full/206/400/416 behavior and emits Content-Range and lengths.
- Test evidence
- tests/byte_ranges/verify.js:92-143 and tests/conditional/verify.js:223-248; both focused suites passed during this assessment.
- Assessment rationale
- The obligation is conditional on a role, status, or feature that Achieve core does not exercise in its supported origin-server behavior.
- Open question
- None recorded.
- V2 traceability
- V2-S060
Optional not implemented Normative level: MAY
- Requirement
- When multiple ranges were requested but only one remains satisfiable or after coalescing, a server MAY generate multipart/byteranges with one body part.
- Conditions
- Only when multiple ranges were requested and selection leaves one part.
- Applicable role
- server
- Responsible layer
- Achieve/application
- Implementation evidence
- achieve.js:3008-3087 parses byte ranges; achieve.js:3132-3204 selects full/206/400/416 behavior and emits Content-Range and lengths.
- Test evidence
- tests/byte_ranges/verify.js:92-143 and tests/conditional/verify.js:223-248; both focused suites passed during this assessment.
- Assessment rationale
- The referenced capability is optional and Achieve does not implement the triggering successful/optional behavior.
- Open question
- None recorded.
- V2 traceability
- V2-S066
Conformant Normative level: MUST
- Requirement
- A 304 server must generate the listed cache/validator fields that the corresponding 200 would have sent.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- sender of a 304 response
- Responsible layer
- Achieve conditional static/media response generation; Node serializes
- Implementation evidence
- The conditional path sets Date before evaluation and explicitly adds current ETag and Last-Modified when selecting 304; representation fields absent from the corresponding 200 are not required.
- Test evidence
- Batch B paired 200 and matching If-None-Match 304 responses over HTTP/1.1 and h2c. Date and ETag appeared on both; Cache-Control, Expires, Content-Location, and Vary were absent from both. The 304 carried no body.
- Assessment rationale
- Every section 15.4.5 listed field that would have appeared on the corresponding 200 was generated on 304.
- Open question
- None for the tested static identity representation.
- V2 traceability
- V2-NEW-028
Conformant Normative level: SHOULD NOT
- Requirement
- A 304 sender should not emit other representation metadata unless useful for cache updates.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
- Applicable role
- sender of a 304 response
- Responsible layer
- Achieve conditional static/media response generation
- Implementation evidence
- The 304 path emits the mandatory Date and ETag plus Last-Modified, a validator used to guide cache updates, and omits Content-Type and other representation metadata.
- Test evidence
- Batch B HTTP/1.1 and h2c 304 responses contained Date, ETag, and Last-Modified, omitted Content-Type, and contained no body. The corresponding 200 supplied the same Last-Modified validator.
- Assessment rationale
- Last-Modified is directly useful for cache validation/update and is the RFC's example of permissible additional 304 metadata; no unnecessary representation metadata was observed.
- Open question
- None for the tested static identity representation.
- V2 traceability
- V2-NEW-029
Conformant Normative level: MUST NOT
- Requirement
- A 304 response MUST NOT contain content.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- HTTP participant
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:970-980 carries a no-body flag for HEAD; achieve.js:1663-1673, achieve.js:2415-2443, and achieve.js:2844-2866 complete responses without bodies where Achieve owns completion; Node enforces protocol framing.
- Test evidence
- tests/response_completion/verify.js:133-242 and tests/static_dates/verify.js:82-98; focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S061
Not applicable Normative level: SHOULD
- Requirement
- A server responding 409 SHOULD generate content with enough information for a user to recognize the source of the conflict.
- Conditions
- Unless the request method or response context precludes content.
- Applicable role
- server
- Responsible layer
- Servlet application when it selects 409; Achieve core does not generate 409
- Implementation evidence
- No Achieve core path selects status 409. Servlets directly control an application-selected 409 status and its explanatory content.
- Test evidence
- Source search found no core 409 generation. Existing response-completion coverage includes an application-selected 409 with no value only as completion semantics, not an Achieve conflict response.
- Assessment rationale
- The conditional recommendation is not reached by Achieve core. A deployed application choosing 409 is responsible for useful conflict information.
- Open question
- None for Achieve core; application conformance depends on the servlet and request context.
- V2 traceability
- V2-S064
Nonconformant Normative level: MUST
- Requirement
- An origin server generating a 405 response MUST generate an Allow field listing the target resource's currently supported methods.
- Conditions
- The origin server generates a 405 response.
- Applicable role
- origin server
- Responsible layer
- Node.js HTTP/2 compatibility layer; complete Achieve endpoint
- Implementation evidence
- Achieve listen2() uses Node's HTTP/2 compatibility server. Node handles classic CONNECT before invoking the compatibility request handler and generates the 405 response.
- Test evidence
- The original focused reproduction assigned the behavior to Node's compatibility layer. Final Node.js 24.22.2 Windows and Linux qualification sent valid classic CONNECT and again observed :status 405 and date with no Allow field; the compatibility request handler was not invoked.
- Assessment rationale
- The qualified Achieve HTTP/2 endpoint generates 405 without the mandatory Allow field. Standalone Node reproduces the behavior, assigning it to Node's compatibility layer rather than Achieve application logic.
- Open question
- Normal Achieve request handling cannot add the field because Node does not dispatch this CONNECT request to it; reassess when the supported Node baseline changes.
- V2 traceability
- V2-S062
Not applicable Normative level: None
- Requirement
- RFC 9110 defines 408 Request Timeout but does not require or recommend a Connection: close field.
- Conditions
- No normative connection-field obligation exists in RFC 9110 section 15.5.9.
- Applicable role
- informational status definition
- Responsible layer
- Inventory correction
- Implementation evidence
- RFC 9110 section 15.5.9 says that a new connection will be used if the current connection is unusable; it contains no MUST, SHOULD, or MAY concerning a Connection field.
- Test evidence
- For operational context only, a bounded Batch C timeout probe observed Node.js 22.15.0 emit HTTP/1.1 408 Request Timeout with Connection: close and close the socket for both Achieve and standalone Node.
- Assessment rationale
- The former SHOULD wording was inherited from superseded RFC 7231 section 6.5.7 and is not a normative RFC 9110 requirement. The V3 identifier is retained for traceability but cannot be a conformance success.
- Open question
- No RFC 9110 conformance verification is required for the removed obligation; Node timeout behavior remains documented as an observation.
- V2 traceability
- V2-S063
Conformant Normative level: SHOULD
- Requirement
- A 500 response SHOULD include a representation explaining the condition unless HEAD or disclosure is inappropriate.
- Conditions
- Apply only under the conditions and exceptions stated in the cited section.
- Applicable role
- HTTP participant
- Responsible layer
- Achieve
- Implementation evidence
- achieve.js:661-735, achieve.js:1663-1674, and achieve.js:2408-2471 cover normal and exceptional Achieve-managed completion.
- Test evidence
- tests/response_completion/verify.js:133-242 and tests/static_dates/verify.js:82-98; focused suites passed during this assessment.
- Assessment rationale
- Direct implementation structure and focused tests adequately establish the stated obligation within Achieve-owned behavior and the tested Node 22 endpoint.
- Open question
- None recorded.
- V2 traceability
- V2-S065