FA-28724 / HTTP redirects / Member archive

Apply a configured redirect query transformation without changing retained value order: empty value kept · case 04

Apply a configured redirect query transformation without changing retained value order: the empty value kept branch emits an incorrect decision.

Member previewVariant 4 · 3 implementations · 7 checks per implementation

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 fixture

This 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"], "#z", ["x", "flag"], [], 0, [], "?"], "request": "/requests/4/3"}`	`{"decision": [[["flag", null]], [["x", ""], ["flag", null]], [["x", ""], ["flag", null]], ["x=", "flag"], "#z", ["x", "flag"], [["x", ""]], 0, [], "?"], "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.