FAILURE MAP
← Case archive

FA-26378 / HTTP ranges / Member archive

An explicit nonmatching entity condition takes precedence over a matching date · case 03

An explicit nonmatching entity condition takes precedence over a matching date.

Member previewVariant 3 · 3 implementations · 6 checks per implementation

Case contract

For this GET model use tag_hit whenever a tag condition was present, otherwise date_hit. Return [304,empty] or [206,part].

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
if-none-match-suppresses-date fixture 0[304, ""][206, "ppp"]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 ↗