FAILURE MAP
← Case archive

FA-26825 / HTTP ranges / Member archive

End-of-stream without a closing delimiter leaves the response incomplete · case 05

End-of-stream without a closing delimiter leaves the response incomplete.

Member previewVariant 5 · 3 implementations · 6 checks per implementation

Case contract

Return [complete,parts] only after closing delimiter; EOF without close is [truncated,empty], otherwise [waiting,parts].

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
multipart-client-close-required fixture 0["complete", ["ppppp"]]["truncated", []]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 ↗