FA-28892 / HTTP redirects / Member archive
Match query-aware redirect rules against repeated decoded query fields: all values selected · case 02
Match query-aware redirect rules against repeated decoded query fields: the all values selected branch emits an incorrect decision.
Case contract
Match query-aware redirect rules against repeated decoded query fields. 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"], ["a", "b"], true, true, false, true, true, 2, true, true], "request": "/requests/2/0"} | {"decision": [["a", "b"], ["a", "b"], true, true, false, true, true, 2, true, true], "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 ↗