FA-28517 / HTTP redirects / Member archive

Select a redirect rule by explicit priority, specificity and declaration order: rule count not target count · case 02

Select a redirect rule by explicit priority, specificity and declaration order: the rule count not target count branch emits an incorrect decision.

Member previewVariant 2 · 3 implementations · 6 checks per implementation

Case contract

Select a redirect rule by explicit priority, specificity and declaration 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 1	`{"decision": [["/x", "/y"], ["/x", "/y"], ["/y", "/x"], ["/x", "/y"], "/y", 1, 2, false, ["/x"], false], "request": "/requests/2/0"}`	`{"decision": [["/x", "/y"], ["/x", "/y"], ["/y", "/x"], ["/x", "/y"], "/y", 2, 2, false, ["/x"], false], "request": "/requests/2/0"}`	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.