414URI Too Long
414 URI Too Long means the server is refusing the request because the target URI is longer than it is willing to interpret. It is rare, and almost always a client-side design problem.
What does it mean?
The usual causes are a POST turned into a GET with a huge query string, a redirect loop that keeps appending to the URL, or an attack probing length limits.
A 414 response is heuristically cacheable. The old reason phrase was “Request-URI Too Long”; RFC 9110 uses “URI Too Long”.
When does it happen?
- A filter or search form puts too much state into the query string.
- A redirect chain appends the same parameters over and over.
- A client sends a huge data payload in the URL instead of the body.
- A WAF or server has a low URI length limit.
How do you fix it?
If you run the server
- Move large payloads to POST, PUT, or PATCH bodies.
- Fix redirect loops before raising the limit.
- If you raise the limit, do it deliberately and log the requests that hit it.
If you are just visiting
- Shorten the URL or use the site search instead of a long filter link.
- If a link from this site caused it, the link is too long; tell us.
