FA-29059 / HTTP redirects / Member archive

Build public redirect origins from explicitly trusted proxy metadata: empty forwarded value fallback · case 04

Build public redirect origins from explicitly trusted proxy metadata: the empty forwarded value fallback branch emits an incorrect decision.

Member previewVariant 4 · 3 implementations · 6 checks per implementation

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 fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
fixture 2	`{"decision": ["public.test", "http", ["attacker.test"], false, "/", "", "public.test", "/", true, "direct"], "request": "/requests/4/1"}`	`{"decision": ["public.test", "http", ["attacker.test"], true, "/", "", "public.test", "/", true, "direct"], "request": "/requests/4/1"}`	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.