FA-28027 / HTTP redirects / Member archive

Validate a redirect port against an explicit bounded port policy: port upper bound · case 02

Validate a redirect port against an explicit bounded port policy: the port upper bound branch emits an incorrect decision.

Member previewVariant 2 · 3 implementations · 6 checks per implementation

Case contract

Validate a redirect port against an explicit bounded port 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 fixture

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

Boundary fixture	Actual	Expected	Outcome
fixture 3	`{"decision": [65535, false, true, false, true], "request": "/requests/2/2"}`	`{"decision": [65535, false, false, false, true], "request": "/requests/2/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.