Achieve — High Level Logic Project. Creating a new meta design pattern.

Friendly in development. Fast in production. Just build your apps. Let Achieve do the rest.

Achieve RFC 9111 HTTP Caching

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 7 authoritative V3 requirements for RFC 9111. Requirement text is a traceable summary; the linked RFC Editor section supplies the controlling normative text and conditions.

ClassificationCount
Conformant0
Nonconformant0
Unverified0
Not applicable3
Optional not implemented4
Total7

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

V3-9111-001 — RFC 9111 §3

Not applicable Normative level: MUST NOT

Requirement
A cache MUST NOT store a response unless every storage condition in §3 is satisfied.
Conditions
Method, status, no-store/private, Authorization, and understood-directive gates all apply.
Applicable role
cache
Responsible layer
external cache
Implementation evidence
achieve.js:430-440 defines representation caching/compression state, but no HTTP cache storage or stored-response reuse component exists; request handling proceeds through achieve.js:944-1049.
Test evidence
No cache storage/reuse tests apply because Achieve does not implement an HTTP cache.
Assessment rationale
Achieve is an origin server and has no HTTP response-storage cache. The section 3 storage gate is imposed on caches.
Open question
No remaining Achieve verification question.
V2 traceability
V2-X029

V3-9111-002 — RFC 9111 §4

Not applicable Normative level: MUST NOT

Requirement
A cache MUST NOT reuse a stored response unless target URI, method, request fields, Vary, freshness/validation, and directive conditions all permit reuse.
Conditions
Every reuse gate in §4 applies.
Applicable role
cache
Responsible layer
external cache
Implementation evidence
achieve.js:430-440 defines representation caching/compression state, but no HTTP cache storage or stored-response reuse component exists; request handling proceeds through achieve.js:944-1049.
Test evidence
No cache storage/reuse tests apply because Achieve does not implement an HTTP cache.
Assessment rationale
Achieve is an origin server and does not reuse stored HTTP responses to satisfy later requests. The section 4 reuse gate is imposed on caches.
Open question
No remaining Achieve verification question.
V2 traceability
V2-X030

V3-9111-003 — RFC 9111 §5.2.2.1

Optional not implemented Normative level: MUST NOT

Requirement
A sender must not quote a response `max-age` delta-seconds value.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
sender
Responsible layer
Achieve/application
Implementation evidence
achieve.js:554-557 toggles validator/browser-caching behavior; achieve.js:1711-1777 generates ETag/Last-Modified, and no Cache-Control directive generation exists. Servlet applications receive the Node response object at achieve.js:1857-1919.
Test evidence
tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195 verify validators and conditional requests, not Cache-Control directive syntax; no focused directive-generation test exists.
Assessment rationale
Achieve core does not generate Cache-Control or max-age. Applications can author response fields through Node response APIs and own their syntax.
Open question
If Achieve later generates max-age, add a focused token-versus-quoted-string test.
V2 traceability
V2-NEW-031

V3-9111-004 — RFC 9111 §5.2.2.10

Optional not implemented Normative level: MUST NOT

Requirement
A sender must not quote an `s-maxage` delta-seconds value.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
sender
Responsible layer
Achieve/application
Implementation evidence
achieve.js:554-557 toggles validator/browser-caching behavior; achieve.js:1711-1777 generates ETag/Last-Modified, and no Cache-Control directive generation exists. Servlet applications receive the Node response object at achieve.js:1857-1919.
Test evidence
tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195 verify validators and conditional requests, not Cache-Control directive syntax; no focused directive-generation test exists.
Assessment rationale
Achieve core does not generate Cache-Control or s-maxage. Applications can author response fields through Node response APIs and own their syntax.
Open question
If Achieve later generates s-maxage, add a focused token-versus-quoted-string test.
V2 traceability
V2-NEW-032

V3-9111-005 — RFC 9111 §5.2.2.4

Optional not implemented Normative level: SHOULD NOT

Requirement
A sender should not use token form for a qualified `no-cache` field-name list.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
sender
Responsible layer
Achieve/application
Implementation evidence
achieve.js:554-557 toggles validator/browser-caching behavior; achieve.js:1711-1777 generates ETag/Last-Modified, and no Cache-Control directive generation exists. Servlet applications receive the Node response object at achieve.js:1857-1919.
Test evidence
tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195 verify validators and conditional requests, not Cache-Control directive syntax; no focused directive-generation test exists.
Assessment rationale
Achieve core does not generate a qualified no-cache directive. Applications that choose to generate one own its field-name-list syntax.
Open question
Correct the ledger role/applicability, then test only if Achieve begins generating the directive.
V2 traceability
V2-NEW-033

V3-9111-006 — RFC 9111 §5.2.2.7

Optional not implemented Normative level: SHOULD NOT

Requirement
A sender should not use token form for a qualified `private` field-name list.
Conditions
Apply only under the conditions and exceptions stated in the cited section and summarized in the requirement.
Applicable role
sender
Responsible layer
Achieve/application
Implementation evidence
achieve.js:554-557 toggles validator/browser-caching behavior; achieve.js:1711-1777 generates ETag/Last-Modified, and no Cache-Control directive generation exists. Servlet applications receive the Node response object at achieve.js:1857-1919.
Test evidence
tests/conditional/verify.js:138-343 and tests/static_dates/verify.js:82-195 verify validators and conditional requests, not Cache-Control directive syntax; no focused directive-generation test exists.
Assessment rationale
Achieve core does not generate a qualified private directive. Applications that choose to generate one own its field-name-list syntax.
Open question
If Achieve later generates qualified private, add a quoted-list test.
V2 traceability
V2-NEW-034

V3-9111-007 — RFC 9111 §5.3

Not applicable Normative level: MUST NOT

Requirement
An origin server without a clock must not generate Expires except for a fixed past value or one assigned by a clocked system.
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/application
Implementation evidence
achieve.js:1770-1777 uses Date.now() and emits Date/Last-Modified; no Expires generation exists in achieve.js. package.json:28 requires Node >=22.
Test evidence
tests/static_dates/verify.js:82-195 verifies clock-derived Date and Last-Modified behavior; it does not exercise a clockless server or Expires.
Assessment rationale
The condition is an origin server without a clock. Achieve 3.0.6 requires Node 22, uses Date.now(), and does not generate Expires in core response paths.
Open question
Reassess only if a supported clockless environment or core Expires generation is introduced.
V2 traceability
V2-NEW-035