FA-29029 / HTTP redirects / Member archive

Invalidate redirect mappings by source and affected target with partition isolation: empty invalidation no hit · case 04

Invalidate redirect mappings by source and affected target with partition isolation: the empty invalidation no hit branch emits an incorrect decision.

Member previewVariant 4 · 3 implementations · 7 checks per implementation

Case contract

Invalidate redirect mappings by source and affected target with partition isolation. 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 5	`{"decision": [[["/a", "/b", "p", true]], [["/a", "/b", "p", true]], [["/a", "/b", "p", true]], [], [], 0, [["/a", "/b", "p", true]], true, false, ["/a"]], "request": "/requests/4/4"}`	`{"decision": [[["/a", "/b", "p", true]], [["/a", "/b", "p", true]], [["/a", "/b", "p", true]], [], [], 0, [["/a", "/b", "p", true]], false, false, ["/a"]], "request": "/requests/4/4"}`	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.