FA-27975 / HTTP redirects / Member archive

Prepare upload metadata and handoff sequencing after a redirect decision: multipart wire boundary · case 05

Reconstructing multipart headers chooses a new boundary although the replayed wire bytes still contain the old boundary.

Member previewVariant 5 · 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 2	`{"decision": [{"Content-Length": "3", "Content-Type": "multipart", "Expect": "100-continue", "Trailer": "X-Sum", "Transfer-Encoding": "chunked", "X": "keep"}, "B", true, ["rewind-upload", "dispatch"], "length"], "request": "/requests/5/1"}`	`{"decision": [{"Content-Length": "3", "Content-Type": "multipart", "Expect": "100-continue", "Trailer": "X-Sum", "Transfer-Encoding": "chunked", "X": "keep"}, "A", true, ["rewind-upload", "dispatch"], "length"], "request": "/requests/5/1"}`	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.