FA-28949 / HTTP redirects / Member archive

Account for a redirect chain using a monotonic deadline and separate response timing: headers latency · case 04

Account for a redirect chain using a monotonic deadline and separate response timing: the headers latency branch emits an incorrect decision.

Member previewVariant 4 · 3 implementations · 6 checks per implementation

Case contract

Account for a redirect chain using a monotonic deadline and separate response timing. 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": [2, 5, 2, 8, false, 1018, 20, 3, false, 5], "request": "/requests/4/0"}`	`{"decision": [2, 3, 2, 8, false, 1018, 20, 3, false, 5], "request": "/requests/4/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.