FA-27989 / HTTP redirects / Member archive

Prepare upload metadata and handoff sequencing after a redirect decision: unknown length framing · case 04

An unknown replay length and a known zero-byte body are assigned the same framing.

Member previewVariant 4 · 3 implementations · 6 checks per implementation

Case contract

Prepare upload metadata and handoff sequencing after a redirect decision. The explicit fixture inputs and outputs define a bounded offline policy; request identity must accompany the decision.

Why this case matters

Models a redirect controller decision before following a target or exposing a redirect result.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
fixture 4	`{"decision": [{}, "B", false, ["rewind-upload", "dispatch"], "chunked"], "request": "/requests/4/3"}`	`{"decision": [{}, "B", false, ["rewind-upload", "dispatch"], "length"], "request": "/requests/4/3"}`	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.