FAILURE MAP
← Case archive

FA-6745 / HTTP caching / Member archive

Request min fresh reserves future freshness · case 05

Request min fresh reserves future freshness.

Member previewVariant 5 · 3 implementations · 4 checks per implementation

Case contract

Bounded offline decision model: request min fresh reserves future freshness. Inputs are already validated protocol fields; the explicit fixtures define the supported policy, not a complete protocol implementation.

Why this case matters

This deterministic http caching model isolates the request-min-fresh-reserves-future-freshness policy at a network component boundary.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixtureActualExpectedOutcome
fixture 2truefalseFailed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.

Sign in to the archive ↗