FA-28474 / HTTP redirects / Member archive
Resolve stored redirect chains with per-entry freshness and provenance: lookup target · case 04
Resolve stored redirect chains with per-entry freshness and provenance: the lookup target branch emits an incorrect decision.
Case contract
Resolve stored redirect chains with per-entry freshness and provenance. 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": [["/b", "/c"], 1, false, 10, "cache", false, "/c", 2, false, ["/b"]], "request": "/requests/4/0"} | {"decision": [["/b", "/c"], 1, false, 10, "cache", false, "/b", 2, false, ["/b"]], "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 ↗