FAILURE MAP
← Case archive

FA-26452 / HTTP ranges / Member archive

Part payloads always precede a framing CRLF · case 02

Part payloads always precede a framing CRLF.

Member previewVariant 2 · 3 implementations · 6 checks per implementation

Case contract

Append one CRLF framing separator regardless of whether payload already ends in CRLF. The payload itself must remain intact.

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-payload-separator fixture 0"xx\r\n""xx\r\n\r\n"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 ↗