FA-26474 / HTTP ranges / Member archive

Top-level range metadata is absent for multipart bodies · case 04

Top-level range metadata is absent for multipart bodies.

Member previewVariant 4 · 3 implementations · 6 checks per implementation

Case contract

Return [top-content-range,part-ranges]. A singleton uses its individual range at top and no per-part list; multiple parts have null top and all per-part ranges.

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-no-top-content-range fixture 0	`["a4", ["a4", "b"]]`	`[null, ["a4", "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.