FA-26795 / HTTP ranges / Member archive

Multipart boundary detection retains an incomplete delimiter suffix across reads · case 05

Multipart boundary detection retains an incomplete delimiter suffix across reads.

Member previewVariant 5 · 3 implementations · 6 checks per implementation

Case contract

Return [complete-prefix,remainder] split at first complete marker in tail+chunk; if absent preserve the entire data as remainder for this bounded buffering model.

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-client-delimiter-split fixture 0	`["", "bX"]`	`["aaaaa", "X"]`	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.