FA-26348 / HTTP ranges / Member archive
A matching cache validator suppresses range unsatisfiability · case 03
A matching cache validator suppresses range unsatisfiability.
Case contract
A matching GET cache validator produces [304,empty]; only stale requests evaluate ranges, yielding 206 or 416.
Why this case matters
Range responses combine representation identity, conditional requests, framing, and partial-object state.
One recorded failure
Sample boundary fixtureThis sample comes from the broken implementation of a controlled reproducer.
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| not-modified-before-unsatisfied fixture 0 | [416, ""] | [304, ""] | Failed |
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 ↗