FA-29089 / HTTP redirects / Member archive
Build public redirect origins from explicitly trusted proxy metadata: proxy metadata provenance · case 04
Build public redirect origins from explicitly trusted proxy metadata: the proxy metadata provenance branch emits an incorrect decision.
Case contract
Build public redirect origins from explicitly trusted proxy metadata. 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": ["fallback.test", "https", [], false, "", "", "fallback.test", "/", true, "forwarded"], "request": "/requests/4/2"} | {"decision": ["fallback.test", "https", [], false, "", "", "fallback.test", "/", true, "direct"], "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 ↗