FA-26342 / HTTP ranges / Member archive
Failed write-independent preconditions precede range parsing · case 02
Failed write-independent preconditions precede range parsing.
Case contract
Return [status,body]: failed If-Match is 412 before examining a malformed range; otherwise malformed range is 400 and valid range 206.
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 |
|---|---|---|---|
| precondition-before-range fixture 0 | [400, ""] | [412, ""] | 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 ↗