FAILURE MAP
← Case archive

FA-26424 / HTTP ranges / Member archive

A range read is rejected if metadata and body revisions diverge · case 04

A range read is rejected if metadata and body revisions diverge.

Member previewVariant 4 · 3 implementations · 6 checks per implementation

Case contract

Pinned response plan requires exact revision equality; return [ok,body] or [restart,empty]. Revisions are nonnegative integers.

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
representation-pin-revision fixture 0["ok", "pppp"]["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 ↗