FA-28842 / HTTP redirects / Member archive

Serialize a redirect response under an explicit server-side response policy: location overwrites stale · case 02

Serialize a redirect response under an explicit server-side response policy: the location overwrites stale branch emits an incorrect decision.

Member previewVariant 2 · 3 implementations · 7 checks per implementation

Case contract

Serialize a redirect response under an explicit server-side response policy. 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": [{"Location": "/stale"}, "", 0, 301, "/b", "/b", "/b", {"Location": "/stale"}, true, false], "request": "/requests/2/4"}`	`{"decision": [{"Location": "/b"}, "", 0, 301, "/b", "/b", "/b", {"Location": "/stale"}, true, false], "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.