FA-27938 / HTTP redirects / Member archive

Apply a configured HTTP redirect scheme policy: implicit scheme upgrade · case 03

An explicit scheme is overwritten by automatic upgrade policy.

Member previewVariant 3 · 3 implementations · 6 checks per implementation

Case contract

Apply a configured HTTP redirect scheme 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": ["", true, false, false, "https"], "request": "/requests/3/2"}`	`{"decision": ["", true, false, false, "http"], "request": "/requests/3/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.