FA-29298 / HTTP redirects / Member archive
Report redirect failures with the failing phase and completed request context: original request retained · case 03
Report redirect failures with the failing phase and completed request context: the original request retained branch emits an incorrect decision.
Case contract
Report redirect failures with the failing phase and completed request context. 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 fixtureThis sample comes from the broken implementation of a controlled reproducer.
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| fixture 1 | {"decision": ["parse", "bad%", "bad%", ["/a"], "invalid-target", true, "/a", true, ["/a"], true], "request": "/requests/3/0"} | {"decision": ["parse", "/a", "bad%", ["/a"], "invalid-target", true, "/a", true, ["/a"], true], "request": "/requests/3/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.
Sign in to the archive ↗