FA-28849 / HTTP redirects / Member archive
Serialize a redirect response under an explicit server-side response policy: head body suppression · case 04
Serialize a redirect response under an explicit server-side response policy: the head body suppression branch emits an incorrect decision.
Case contract
Serialize a redirect response under an explicit server-side response policy. 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 3 | {"decision": [{"Content-Length": "999", "Location": "/unicode/\u00e9"}, "caf\u00e9", 5, 307, "/unicode/\u00e9", "/unicode/\u00e9", "/unicode/\u00e9", {"Content-Length": "999"}, false, false], "request": "/requests/4/2"} | {"decision": [{"Content-Length": "999", "Location": "/unicode/\u00e9"}, "", 5, 307, "/unicode/\u00e9", "/unicode/\u00e9", "/unicode/\u00e9", {"Content-Length": "999"}, false, false], "request": "/requests/4/2"} | 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 ↗