FA-26397 / HTTP ranges / Member archive
Range metadata uses the negotiated variant length · case 02
Range metadata uses the negotiated variant length.
Case contract
Return content-range metadata as [start,stop,selected-length] for already valid inclusive bounds; selected encoding is identity or encoded.
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 |
|---|---|---|---|
| selected-length-metadata fixture 0 | [0, 1, 12] | [0, 1, 6] | 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 ↗