FA-29164 / HTTP redirects / Member archive
Extract redirect route captures under an explicit segment-matching grammar: terminal empty segment kept · case 04
Extract redirect route captures under an explicit segment-matching grammar: the terminal empty segment kept branch emits an incorrect decision.
Case contract
Extract redirect route captures under an explicit segment-matching grammar. 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 5 | {"decision": ["/a//b/", "a", "a//b/", true, ["api", "a", "b"], "/api/a//b", false, ["a", "", "b", ""], 5, true], "request": "/requests/4/4"} | {"decision": ["/a//b/", "a", "a//b/", true, ["api", "a", "", "b", ""], "/api/a//b", false, ["a", "", "b", ""], 5, true], "request": "/requests/4/4"} | 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 ↗