FA-28199 / HTTP redirects / Member archive
Apply redirect interception to the current hop before validating and dispatching the selected target: response status is hop evidence · case 04
Apply redirect interception to the current hop before validating and dispatching the selected target: the response status is hop evidence branch emits an incorrect decision.
Case contract
Apply redirect interception to the current hop before validating and dispatching the selected target. 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": ["https://c/z", 200, true, "https://b/y", [["X", "1"], ["X", "2"]], true, true, true, true, null], "request": "/requests/4/0"} | {"decision": ["https://c/z", 302, true, "https://b/y", [["X", "1"], ["X", "2"]], true, true, true, true, null], "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.
Sign in to the archive ↗