FAILURE MAP
← Case archive

FA-26747 / HTTP ranges / Member archive

A continuation response must start at the saved prefix boundary · case 02

A continuation response must start at the saved prefix boundary.

Member previewVariant 2 · 3 implementations · 6 checks per implementation

Case contract

Return [append,body] only when returned_start equals saved length; a mismatching start requests restart with empty output.

Why this case matters

Range responses combine representation identity, conditional requests, framing, and partial-object state.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixtureActualExpectedOutcome
resume-content-range-start fixture 0["append", "pp"]["restart", ""]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 ↗