Achieve RFC 9111 HTTP Caching
Created November 6, 2026 · Updated November 6, 2026 · Achieve 3.1.0 · Qualified runtime: Node.js 24.22.2
Requirement levels: RFC 9111 primarily governs caches. The origin-server obligations relevant to Achieve arise only when it generates particular cache metadata or directives.
Achieve is a Node.js HTTP application server, not a shared or private HTTP cache. It supplies representation metadata that browsers and intermediary caches can use, while storage, freshness, reuse, validation, and invalidation decisions remain the cache's responsibility.
Applicable requirements
- MUST NOT: Under RFC 9111 §5.2.2.1, a sender that generates response
max-agemust not quote its delta-seconds value. - MUST NOT: Under §5.2.2.10, a sender that generates
s-maxagemust not quote its delta-seconds value. - SHOULD NOT: Under §5.2.2.4 and §5.2.2.7, a sender should not use token form for a qualified field-name list on
no-cacheorprivate. - MUST NOT: Under §5.3, an origin server without a clock must not generate
Expiresexcept for the stated past-value cases.
Achieve does not automatically generate Cache-Control, Expires, max-age, or s-maxage. The directive-form obligations are optional behavior not implemented by Achieve; application-authored fields remain the application's responsibility. Achieve has a clock through Node.js, so the clockless-origin condition does not apply to its generated responses.
Origin-server metadata
setCaching(true) enables normal advertisement of ETag and Last-Modified for static and media representations. Identity, gzip, and deflate representations receive distinct strong entity tags. Their construction is described in Achieve RFC 9110 §8.8.3 ETag.
Achieve evaluates If-Match, If-Unmodified-Since, If-None-Match, and If-Modified-Since. A successful GET or HEAD revalidation can produce 304; a failed precondition can produce 412. See Conditional Requests for precedence and comparison rules.
Disabling caching stops normal validator advertisement but does not disable all precondition processing. Client-supplied preconditions can still affect a response when Achieve can determine the relevant representation metadata.
Representation selection and reuse
When compression negotiation applies, Achieve sends Vary: Accept-Encoding so caches can distinguish the selected representation. A 304 response retains the applicable validator and selection metadata. Partial-response combination is governed by RFC 9111 §3.4 and is performed by a cache, not by Achieve; see Range Requests and Partial Responses.
Verification
Conditional, static-date, compression, and byte-range suites verify validator advertisement, representation-specific entity tags, 304 and 412 behavior, Vary, changed-source handling, and partial-response metadata across HTTP, HTTPS, h2c, and secure HTTP/2. These tests establish Achieve's origin behavior, not universal behavior of external caches.
Limits and responsibility
RFC 9111's requirements for storing, reusing, calculating freshness, validating, and invalidating responses apply to external caches and are not Achieve origin-server functions. Applications can add their own cache directives through the Node response object; correctness of application-authored policy is outside Achieve's automatic caching facility.
