FA-28765 / HTTP redirects / Member archive

Commit a redirect chain using terminal document semantics and the original navigation intent: replace intent not implied by redirect · case 05

Commit a redirect chain using terminal document semantics and the original navigation intent: the replace intent not implied by redirect branch emits an incorrect decision.

Member previewVariant 5 · 3 implementations · 6 checks per implementation

Case contract

Commit a redirect chain using terminal document semantics and the original navigation intent. 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": [["https://c/z"], false, {"view": "v"}, 1, true, "https://start/home", ["https://b/y"], "c", "document", {"committed": "https://c/z", "requested": "https://a/x"}], "request": "/requests/5/0"}`	`{"decision": [["https://c/z"], false, {"view": "v"}, 1, false, "https://start/home", ["https://b/y"], "c", "document", {"committed": "https://c/z", "requested": "https://a/x"}], "request": "/requests/5/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.