FA-29232 / HTTP redirects / Member archive
Compose explicit redirect policy decisions with veto precedence and reason retention: veto count · case 02
Compose explicit redirect policy decisions with veto precedence and reason retention: the veto count branch emits an incorrect decision.
Case contract
Compose explicit redirect policy decisions with veto precedence and reason retention. 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": [false, "host", ["host"], true, false, false, ["scheme", "host", "port"], false, 3, false], "request": "/requests/2/0"} | {"decision": [false, "host", ["host"], true, false, false, ["scheme", "host", "port"], false, 1, false], "request": "/requests/2/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 ↗