The parks inventory client raises a local socket read deadline before any HTTP status line arrives from Meraki. How does that event differ from receiving an HTTP 408 response body?
Select an answer to reveal the explanation.
Short Explanation
One clock is on your wrist; the other is a reply letter from city hall. A local read deadline rings before any status arrives. A 408 is the server answering with a timeout status and body.
Full Explanation
Client-side socket or read deadlines are detected inside the consumer before a status line exists. HTTP 408 is a server-generated response. Both may be retryable timeouts in the same robustness family, but the detector is not 'parse status 408' for a pure client deadline. Conflating them leads to wrong logging and wrong branches.