FA-26817 / HTTP ranges / Member archive
Each received part needs its own explicit range metadata · case 02
Each received part needs its own explicit range metadata.
Case contract
parts are [content-range-or-null,body]. Return bodies only when every part has range metadata; never inherit a preceding range.
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 |
|---|---|---|---|
| multipart-client-missing-range fixture 0 | ["aa", "b"] | 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 ↗