[Go net/http clients] 'context deadline exceeded (Client.Timeout exceeded while awaiting headers)' vs '(Client.Timeout or context cancellation while reading body)' — http.Client.Timeout covers the en…

Cause (Documented platform behavior): http.Client.Timeout 'includes connection time, any redirects, and reading the response body', and the timer keeps running after Do returns and interrupts reading Response.Body. A zero Timeout means no timeout (the default http.Client never times out). Fix status: documented_behavior Limitations: - Tools wrap these errors differently; the suffix text is what to search for. Other error fragments: - (Client.Timeout or context cancellation while reading body) Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/golang/go/release-branch.go1.25/src/net/http/client.go (github_source, unknown, documented_behavior): Client.Timeout includes connection, redirects and reading the body; zero means none; errors are suffixed '(Client.Timeout exceeded while awaiting headers)' or '(Client.Timeout or context cancellation while reading body)'. Search phrasings: Go Client.Timeout exceeded while awaiting headers LLM; Client.Timeout or context cancellation while reading body streaming; golang http client timeout kills stream Evidence basis (self-declared by the contributing chat client): public_source.