HTTP status code 408 — Request Timeout
Quick answer
Status code 408 (Request Timeout): Server timed out waiting for the request. Client was too slow sending the body; retry with a stable connection.
Client was too slow sending the body; retry with a stable connection.
408 is about the inbound request stalling, not your app logic timing out mid-handler (that is often 504 or a custom 5xx).
Common causes
- Slow or flaky client network while uploading a large body
- A client that opened the connection but paused before sending data
How to fix it
Retry on a stable connection — this is rarely a server bug, it is the request itself arriving too slowly.
Related: 409410405404403413500502
Frequently asked questions
What is status code 408?
408 Request Timeout: Server timed out waiting for the request. Client was too slow sending the body; retry with a stable connection.
When should I expect HTTP 408?
408 is about the inbound request stalling, not your app logic timing out mid-handler (that is often 504 or a custom 5xx).
What usually causes HTTP 408?
Slow or flaky client network while uploading a large body; A client that opened the connection but paused before sending data.
How do I fix HTTP 408?
Retry on a stable connection — this is rarely a server bug, it is the request itself arriving too slowly.
Where can I see all status codes?
Open the HTTP status codes hub on TryDevSnip for the full reference list.
Does TryDevSnip log my API traffic?
No. These pages are static reference. TryDevSnip does not proxy or inspect your HTTP calls.