FAILURE MAP
← Case archive

FA-26510 / HTTP ranges / Member archive

Fragment admission rejects a conflicting complete length · case 05

Fragment admission rejects a conflicting complete length.

Member previewVariant 5 · 3 implementations · 6 checks per implementation

Case contract

Known and incoming complete lengths are integer or None. Reject conflicting known lengths; otherwise return [resolved-length,body].

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
cache-total-length-disagreement fixture 0[6, "ppppp"]nullFailed

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 ↗