FA-28874 / HTTP redirects / Member archive

Serialize a redirect response under an explicit server-side response policy: fragment location preserved · case 04

Serialize a redirect response under an explicit server-side response policy: the fragment location preserved 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 2	`{"decision": [{"Location": "/a#part"}, "next", 4, 303, "/a#part", "/a#part", "/a", {}, false, true], "request": "/requests/4/1"}`	`{"decision": [{"Location": "/a#part"}, "next", 4, 303, "/a#part", "/a#part", "/a#part", {}, false, true], "request": "/requests/4/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.