FA-26730 / HTTP ranges / Member archive
A byte-range client rejects partial metadata in a different unit · case 05
A byte-range client rejects partial metadata in a different unit.
Case contract
Parsed units are case-normalized tokens. Accept payload only when units match exactly; otherwise None.
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 |
|---|---|---|---|
| content-range-unit-mismatch fixture 0 | "ppppp" | null | 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 ↗