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.

← Back to technical specifications

Achieve RFC 9110 HTTP Dates and Last-Modified

Created November 6, 2026 · Updated November 6, 2026 · Achieve 3.1.0 · Qualified runtime: Node.js 24.22.2

Requirement levels: Applicable MUST, MUST NOT, SHOULD, SHOULD NOT, and MAY requirements are labeled below.

Achieve uses HTTP dates for response origination time, static-resource modification metadata, and date-based preconditions. HTTP dates have one-second protocol resolution even when filesystem timestamps are more precise.

HTTP-date formats

Achieve's conditional-date parser recognizes the three exact HTTP formats, rejects non-HTTP extensions and date lists, validates calendar fields, handles a leap-second value, and applies the RFC 850 50-year rule. Generated values use Node's UTC IMF-fixdate serialization.

Date response field

For static and audiovisual processing, Achieve records one origination instant, writes its Date value, and uses that same instant when clamping future modification metadata. For ordinary Node-generated responses, Node's response serializer supplies its automatic Date field unless application code deliberately changes that native behavior. Achieve's direct unsupported-CONNECT response also generates a current IMF-fixdate value.

Last-Modified generation

Achieve derives static and audiovisual modification time from the metadata of the opened selected representation. It rounds down to whole seconds and clamps a future filesystem time to the response's origination instant. When browser caching is enabled, the resulting value is sent as Last-Modified. When caching is disabled, Achieve does not advertise that field on a normal response, but it can still use the selected representation's modification time to evaluate a supplied precondition.

Dynamic servlet responses do not receive an automatic Achieve Last-Modified value. A servlet that authors one is responsible for its relationship to the selected representation.

Date preconditions and precision

If-Modified-Since applies to GET and HEAD when no If-None-Match is present. If-Unmodified-Since is evaluated when no If-Match is present. Invalid dates, date lists, and conditions without available modification metadata are ignored as required. Achieve compares whole-second values: an unchanged or earlier representation can produce 304 for If-Modified-Since, while a representation newer than If-Unmodified-Since produces 412.

One-second resolution cannot distinguish two changes within the same second. Achieve's strong ETag contains finer filesystem change metadata, so entity-tag preconditions take precedence and can distinguish changes that share one Last-Modified value. See Conditional Requests and ETag Validators.

Date-validator strength and If-Range

Under RFC 9110 §8.8.2.2, a modification date is implicitly weak unless the origin server reliably knows that the representation did not change twice during the represented second, or one of the RFC's cache-based deductions establishes strength. Exact equality with Last-Modified alone is not sufficient.

Section 13.1.5 requires a date-form If-Range condition to be false unless the supplied date is a strong validator and exactly matches the selected representation's Last-Modified value. Achieve's current resource model does not establish the required strong-date guarantee, so it conservatively treats date-form If-Range as false and sends the complete selected representation instead of a 206. Matching strong entity tags remain supported for If-Range. See Range Requests and Partial Responses.

Automated verification and limits

The static-date verifier runs over HTTP, HTTPS, h2c, and secure HTTP/2. It covers all three accepted formats, invalid values and lists, the RFC 850 year boundary, GET and HEAD, If-Modified-Since and If-Unmodified-Since comparisons and precedence, future-time clamping, compressed and identity representations, same-second changes, date-form If-Range fallback, disabled validator advertisement, servlet exclusion, descriptor cleanup, and pathname replacement after the representation is opened.

Those tests establish Achieve's static and media paths on Node.js 24.22.2; they do not establish the correctness of arbitrary application-authored dates or clocks. Filesystem timestamp quality and system-clock synchronization remain deployment properties.