FA-27847 / HTTP redirects / Member archive

Select an unambiguous Location field without losing raw syntax: duplicate field rejection · case 02

Other headers are confused with duplicate redirect targets.

Member previewVariant 2 · 3 implementations · 6 checks per implementation

Case contract

Select an unambiguous Location field without losing raw syntax. 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 5	`{"decision": [["/a", "/b"], false, ["/a", "/b"], ["/a", "/b"], "present"], "request": "/requests/2/4"}`	`{"decision": [["/a", "/b"], true, ["/a", "/b"], ["/a", "/b"], "present"], "request": "/requests/2/4"}`	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.