FA-28045 / HTTP redirects / Member archive
Keep encoded path structure distinct from redirect routing structure: encoded slash preservation · case 05
Keep encoded path structure distinct from redirect routing structure: the encoded slash preservation branch emits an incorrect decision.
Case contract
Keep encoded path structure distinct from redirect routing structure. 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": [["", "a", "b", "%2F"], "/a%2Fb/%252F", "/a%2Fb/%252F", "/a/b/%2F", []], "request": "/requests/5/0"} | {"decision": [["", "a%2Fb", "%252F"], "/a%2Fb/%252F", "/a%2Fb/%252F", "/a/b/%2F", []], "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.
Sign in to the archive ↗