FA-26480 / HTTP ranges / Member archive

Multipart assembly preserves the normalized request order · case 05

Multipart assembly preserves the normalized request order.

Member previewVariant 5 · 3 implementations · 6 checks per implementation

Case contract

Parts are [request-position,absolute-start,payload]. Return payloads ordered by request-position, not by byte offset or arrival order. Positions unique.

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 fixture	Actual	Expected	Outcome
multipart-part-order fixture 0	`["b", "a"]`	`["a", "b"]`	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.