| Previous | Next |
| HTTP_STATUS_UNAUTHORIZED |
HTTP_STATUS_NETWORK_READ_TIMEOUT
Meaning and context of HTTP_STATUS_NETWORK_READ_TIMEOUT
598 Network read timeout error is not registered in the HTTP status-code registry. Its interpretation therefore depends on the proxy or middleware that emitted it. In the commonly used convention, the proxy connected to the upstream successfully but did not receive a complete response before its read timer expired.
The important distinction is the phase of the failed request. A read timeout points after connection establishment: the upstream may be stalled in application code, waiting on a database or another dependency, blocked while streaming a response, or separated from the proxy by a degraded network path. By contrast, the related informal 599 convention is generally used for a connection timeout before an upstream connection is completed.
Identify the emitting product from response headers, configuration, and proxy logs before assuming fixed semantics. Then correlate one request across the proxy and upstream using a request ID and timestamps for connection acceptance, request handoff, first response byte, and final byte. Raising a read timeout can be appropriate for a deliberately long operation, but it does not repair a blocked dependency or an upstream that stops making progress.
IANA HTTP Status Code Registry · RFC 9110: HTTP Semantics · 598 Network Read Timeout Error reference
Looking for a different code? Search another status or error code.