FAILURE MAP
← Case archive

FA-26798 / HTTP ranges / Member archive

Boundary-like substrings inside part bodies remain payload data · case 03

Boundary-like substrings inside part bodies remain payload data.

Member previewVariant 3 · 3 implementations · 6 checks per implementation

Case contract

Return position of first delimiter at start or immediately after CRLF, or -1. Delimiter bytes are --boundary; interior lookalikes are ignored.

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-line-anchoring fixture 01-1Failed

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 ↗