FAILURE MAP
← Case archive

FA-26495 / HTTP ranges / Member archive

Cached fragments with different validators cannot be joined · case 05

Cached fragments with different validators cannot be joined.

Member previewVariant 5 · 3 implementations · 6 checks per implementation

Case contract

Fragments are [strong-validator,payload] in byte order. Return their joined body when all validators agree, None otherwise; no fragments returns empty.

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-revision-splice fixture 0"xxxxxy"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 ↗