FA-29175 / HTTP redirects / Member archive

Extract redirect route captures under an explicit segment-matching grammar: literal period not wildcard · case 05

Extract redirect route captures under an explicit segment-matching grammar: the literal period not wildcard branch emits an incorrect decision.

Member previewVariant 5 · 3 implementations · 7 checks per implementation

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 fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
fixture 1	`{"decision": ["/a/b", "a", "a/b", true, ["api", "a", "b"], "/api/a/b", true, ["a", "b"], 3, true], "request": "/requests/5/0"}`	`{"decision": ["/a/b", "a", "a/b", true, ["api", "a", "b"], "/api/a/b", false, ["a", "b"], 3, true], "request": "/requests/5/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.