FA-27969 / HTTP redirects / Member archive

Prepare upload metadata and handoff sequencing after a redirect decision: entity metadata clearing · case 04

Removing only Content-Length leaves stale entity metadata attached to a rewritten request.

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 1	`{"decision": [{"Content-Length": "3", "Content-Type": "multipart", "Expect": "100-continue", "Trailer": "X-Sum", "Transfer-Encoding": "chunked", "X": "keep"}, "B", false, ["abort-upload", "clear-entity", "dispatch"], "none"], "request": "/requests/4/0"}`	`{"decision": [{"X": "keep"}, "B", false, ["abort-upload", "clear-entity", "dispatch"], "none"], "request": "/requests/4/0"}`	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.