FA-27322 / HTTP ranges / Member archive

A range client removes transfer framing before applying representation offsets: range offsets address decoded payload rather than transfer framing · case 02

A range client removes transfer framing before applying representation offsets: range offsets address decoded payload rather than transfer framing.

Member previewVariant 2 · 3 implementations · 11 checks per implementation

Case contract

Decode a complete bounded ASCII chunked origin body. Size lines use 1..2 hexadecimal digits with optional semicolon extensions, followed by exact CRLF; each data chunk has exact trailing CRLF. A zero chunk ends data and introduces colon-bearing trailer lines terminated by an empty CRLF line. No bytes may follow trailers. Enforce cumulative decoded-byte limit x.limit. Return [decoded[start:stop],decoded-length,trailer-lines] or None. This controlled framing model does not implement general HTTP headers.

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
decoded-slice fixture 0	`["foo=", 10, ["X:y"]]`	`["2345", 10, ["X:y"]]`	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.