FA-28708 / HTTP redirects / Member archive
Apply a configured redirect query transformation without changing retained value order: bare field serialization · case 03
Apply a configured redirect query transformation without changing retained value order: the bare field serialization branch emits an incorrect decision.
Case contract
Apply a configured redirect query transformation without changing retained value order. 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": [[["flag", null]], [["x", ""], ["flag", null]], [["x", ""], ["flag", null]], ["x=", "flag=None"], "#z", ["x", "flag"], [["x", ""]], 0, [], "?"], "request": "/requests/3/3"} | {"decision": [[["flag", null]], [["x", ""], ["flag", null]], [["x", ""], ["flag", null]], ["x=", "flag"], "#z", ["x", "flag"], [["x", ""]], 0, [], "?"], "request": "/requests/3/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 ↗