FA-28864 / HTTP redirects / Member archive

Serialize a redirect response under an explicit server-side response policy: html target ampersand · case 04

Serialize a redirect response under an explicit server-side response policy: the html target ampersand branch emits an incorrect decision.

Member previewVariant 4 · 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 1	`{"decision": [{"Location": "/a?x=1\u0026y=2", "X": "v"}, "move", 4, 302, "/a?x=1\u0026y=2", "/a?x=1\u0026y=2", "/a?x=1\u0026y=2", {"X": "v"}, false, false], "request": "/requests/4/0"}`	`{"decision": [{"Location": "/a?x=1\u0026y=2", "X": "v"}, "move", 4, 302, "/a?x=1\u0026amp;y=2", "/a?x=1\u0026y=2", "/a?x=1\u0026y=2", {"X": "v"}, false, false], "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.