[alexluong]

When a receiver closes the connection after we send the request but before it responds, Go's HTTP client returns a bare EOF. ClassifyNetworkError only matches "connection reset" in the error text, so these attempts are recorded as the catch-all network_error, which reads like a failure on Outpost's side.

This shows up most with a forward proxy (DESTINATIONS_PROXY_URL). Inside a CONNECT tunnel, an upstream reset reaches Outpost as the proxy closing its side of the tunnel, so the client sees EOF. The same receiver behavior is recorded as connection_reset on a direct delivery and as network_error through the proxy.

ClassifyNetworkError now maps io.EOF and io.ErrUnexpectedEOF to connection_reset, whose documented meaning, "connection was dropped by the server", already covers a close before a response. Retries are unchanged: both codes are destination errors and nothing branches on either.

🤖 Generated with Claude Code