A 408 is the opposite of a 504. Instead of your server being too slow, the visitor's side was too slow to send the request, and the server gave up waiting. It's usually a weak or unstable connection, or a large upload over slow internet. Occasional 408s are normal. Lots of them point to slow uploads or a server timeout set too short.
What's the problem
A page or form shows "408 Request Timeout", most often when uploading files, on mobile connections, or on slow networks.
Why it happens
- A slow or dropping connection on the visitor's side.
- Large uploads that take longer than the server's timeout.
- The server's timeout for receiving requests is set very short.
- Something between the visitor and the server, such as a proxy or corporate firewall, slowing the request down.
How to fix it
- Try again on a better connection. If it works, the connection was the cause.
- If uploads fail, reduce file sizes, compress images before upload, or upload in smaller pieces.
- Check the server's request timeout settings if 408s are common for normal use.
- Check if it's widespread. Many 408s from many visitors suggest a server setting, not their connections.
What Preventionlabs checks
One click runs the full report on your domain. For this problem it shows whether your site loads, how fast, and where its redirects go; up to 50 pages from your sitemap, listing any that fail or are slow, plus broken links on them. With Cloudflare connected, it also shows which pages returned server errors (5xx) to visitors, and when; which requests the firewall blocked, by Cloudflare's own rule names; recent deploys and account changes, with their times.
Run your free reportYour first report is free, no card needed. Then A$50 a month, up to 10 domains. Read-only: it never changes anything.
Sources
- MDN Web Docs: 408 Request Timeoutreference
The HTTP 408 Request Timeout client error response status code indicates that the server would like to shut down this unused connection.