FA-26370 / HTTP ranges / Member archive
A date validator with uncertain revision ordering falls back to the full representation · case 05
A date validator with uncertain revision ordering falls back to the full representation.
Case contract
The local If-Range date policy permits [206,part] only for equal dates backed by stable revision ordering; otherwise [200,full].
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 |
|---|---|---|---|
| if-range-date-strength fixture 0 | [206, "ppppp"] | [200, "fullfullfullfullfull"] | 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 ↗