FA-27378 / HTTP ranges / Member archive

A persisted partial-response cache record keeps byte coverage and revision metadata intact: stored fragment data cannot extend past the recorded representation · case 03

A persisted partial-response cache record keeps byte coverage and revision metadata intact: stored fragment data cannot extend past the recorded representation.

Member previewVariant 3 · 3 implementations · 10 checks per implementation

Case contract

Decode this stipulated local binary cache envelope: magic RG, version1, flags0, two-byte big-endian generation, two-byte big-endian complete length, one-byte fragment count, then fragments [two-byte big-endian offset,one-byte count,ASCII payload], followed by one checksum byte equal to sum of preceding bytes modulo256. Reject malformed envelopes, bytes outside0..255, trailing bytes, overlapping fragment ownership, or spans outside complete length. Return [generation,total,[[offset,payload],...]]. This is an invented bounded persistence format, not a public protocol.

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
span-complete-length fixture 7	`[0, 1, [[0, "ab"]]]`	`null`	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.