FA-7013 / Proxy forwarding / Member archive
Proxy error status distinguishes timeout from connect failure · case 03
Proxy error status distinguishes timeout from connect failure.
Case contract
Bounded offline decision model: proxy error status distinguishes timeout from connect failure. Inputs are already validated protocol fields; the explicit fixtures define the supported policy, not a complete protocol implementation.
Why this case matters
This deterministic proxy forwarding model isolates the proxy-error-status-distinguishes-timeout-from-connect-failure policy at a network component boundary.
One recorded failure
Sample boundary fixtureThis sample comes from the broken implementation of a controlled reproducer.
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| fixture 4 | 200 | 504 | 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.
Sign in to the archive ↗