This article provides a clear visual breakdown of the parts of the HTTP transaction that timeouts such as
http.Client.Timeout cover. However, I was still left with the following question (applicable to outgoing requests from a client): What parts of the HTTP transaction does a request context deadline cover?. From a few test runs, it seems to be equivalent to
HTTP.client.Timeout in the sense that it covers the entire transaction all the way through reading the response body.