FA-28369 / HTTP redirects / Member archive
Partition redirect cache entries by their declared request dimensions: query order and duplicates · case 04
Partition redirect cache entries by their declared request dimensions: the query order and duplicates branch emits an incorrect decision.
Case contract
Partition redirect cache entries by their declared request dimensions. 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 4 | {"decision": ["http", "z.test", 8080, "GET", "/b", "a=1\u0026b=2", true, "tab3", ["en", "br"], 2], "request": "/requests/4/3"} | {"decision": ["http", "z.test", 8080, "GET", "/b", "b=2\u0026a=1\u0026b=2", true, "tab3", ["en", "br"], 2], "request": "/requests/4/3"} | 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 ↗