FA-29823 / HTTP retries / Member archive

Expect-Continue request retry phases: Wait expiry violates retry transition semantics · case 03

Wait expiry violates retry transition semantics

Member previewVariant 3 · 3 implementations · 7 checks per implementation

Case contract

start(body size) starts awaiting permission. interim100 permits sending; other interim messages do not. tick permits optimistic sending after wait expiry. send(bytes) emits at most remaining body only in permitted phase. final(status) stops body transmission and records response. fail permits retry with the same full body only if zero body bytes were sent; otherwise ambiguous. retry resets the handshaking phase after retry permission. Return transmissions and decisions.

Why this case matters

Offline deterministic model of HTTP request retries.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
2	`[["retry", "restarted", "blocked", "blocked"], 0]`	`[["retry", "restarted", "blocked", 3], 3]`	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.