FA-28820 / HTTP redirects / Member archive

Apply post-redirect fragment navigation without altering request routing: text directive routing · case 05

Apply post-redirect fragment navigation without altering request routing: the text directive routing branch emits an incorrect decision.

Member previewVariant 5 · 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 9	`{"decision": [null, ":~:text=no", false, 0, false, true, "", false, 8, ":~:text=no"], "request": "/requests/5/8"}`	`{"decision": [null, ":~:text=no", false, 0, false, false, "", false, 8, ":~:text=no"], "request": "/requests/5/8"}`	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.