FAILURE MAP
← Case archive

FA-26804 / HTTP ranges / Member archive

A longer boundary prefix is not mistaken for the chosen delimiter · case 04

A longer boundary prefix is not mistaken for the chosen delimiter.

Member previewVariant 4 · 3 implementations · 6 checks per implementation

Case contract

A delimiter line equals --boundary or --boundary--; lines are already stripped of CRLF. Return part, close, or payload.

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-boundary-token-end fixture 0"part""payload"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 ↗