FA-26998 / HTTP ranges / Member archive

A client serializes a typed range request plan: open selectors keep an empty final component · case 03

A client serializes a typed range request plan: open selectors keep an empty final component.

Member previewVariant 3 · 3 implementations · 7 checks per implementation

Case contract

Input x contains selectors [kind,a,b], validator [tag|date,value] or null, and accept encoding policy. Closed selectors serialize a-b, open selectors a-, suffix selectors -a, in input order. Empty selectors omit Range and If-Range. Tag validators are quoted opaque ASCII strings without quotes/backslashes; dates are already formatted and remain unquoted. Identity-only policy emits Accept-Encoding identity. Return ordered [header,value] pairs.

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
open-format fixture 1	`[["Range", "bytes=5"], ["If-Range", "Mon, 01 Jan 2001 00:00:00 GMT"]]`	`[["Range", "bytes=5-"], ["If-Range", "Mon, 01 Jan 2001 00:00:00 GMT"]]`	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.