FA-28829 / HTTP redirects / Member archive

Apply post-redirect fragment navigation without altering request routing: anchor existence after decode · case 04

Apply post-redirect fragment navigation without altering request routing: the anchor existence after decode branch emits an incorrect decision.

Member previewVariant 4 · 3 implementations · 10 checks per implementation

Case contract

Apply post-redirect fragment navigation without altering request routing. 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 7	`{"decision": [null, "a b", false, 0, false, false, "", false, 5, "a%20b"], "request": "/requests/4/6"}`	`{"decision": [null, "a b", false, 0, false, false, "", true, 5, "a%20b"], "request": "/requests/4/6"}`	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.