FAILURE MAP
← Case archive

FA-26457 / HTTP ranges / Member archive

Multipart response type carries a boundary rather than the object media type · case 02

Multipart response type carries a boundary rather than the object media type.

Member previewVariant 2 · 3 implementations · 6 checks per implementation

Case contract

Return the stipulated ASCII top-level type multipart/byteranges; boundary="value". Boundary has only letters/digits and may be empty in this framing-unit test.

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-top-content-type fixture 0"text/plain""multipart/byteranges; boundary=\"b2\""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 ↗