FA-27105 / HTTP ranges / Member archive
A bounded Content-Range upload endpoint validates chunk admission: future as well as stale generations require a new session plan · case 05
A bounded Content-Range upload endpoint validates chunk admission: future as well as stale generations require a new session plan.
Case contract
This stipulated endpoint accepts PUT chunks against an upload session. Inputs include session ID, generation, declared complete length, [start,stop) byte span, ASCII body, and known committed cells. Return a disposition and updated cells; malformed metadata never mutates stored bytes. Exact duplicate chunks are idempotent, contradicting overlap is conflict, and quota concerns the complete representation rather than chunk size.
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 |
|---|---|---|---|
| generation-binding fixture 3 | ["partial", [[0, "a"]]] | ["generation", []] | 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 ↗