FA-6670 / HTTP retries / Member archive

An unsafe request cannot replay after any bytes may have reached the peer · case 05

An unsafe request cannot replay after any bytes may have reached the peer.

Member previewVariant 5 · 3 implementations · 4 checks per implementation

Case contract

An unsafe request cannot replay after any bytes may have reached the peer: return the result specified by the explicit input/output boundary fixtures.

Why this case matters

This deterministic http retries model isolates the retry-partial-write policy at a network component boundary.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
fixture 2	`false`	`true`	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.