HTTP 414 URI Too Long (Request-URI Too Long)
Updated Free mock REST & WebSocket APIs
HTTP 414 URI Too Long — The URL is longer than the server is willing to interpret.
- Class
- 4xx Client Error
- Defined in
- RFC 9110 §15.5.15
- Official
- Yes (IANA registry)
- Cacheable by default
- Yes (heuristically, per RFC 9110)
- Safe to retry
- Not without changing the request
Try it: get a real 414 response
Our test endpoint answers every request with 414 URI Too Long.
curl -i https://mockfox.dev/api/status/414Use it in tests, health-check monitors or to see how your client handles a 414. Add ?delay=2000 to slow it down.
What does HTTP 414 mean?
Typically caused by a GET form with huge inputs, a redirect loop that keeps appending query parameters, or data that should be in a POST body. Limits vary: nginx's default large_client_header_buffers is 8 KB per line, Apache's LimitRequestLine 8190 bytes, and browsers cap URLs around 2 MB (Chrome). Move large data into the request body.
Also known as: Request-URI Too Long.
How to fix 414
- Visitors: Reload the page, check the address for typos, and clear the site's cookies. If it persists, the site owner needs to fix it.
- Developers: Read the response body and server logs for details, fix the request (method, headers, body, credentials) and return a clear error message to clients.
Example 414 response
HTTP/1.1 414 URI Too Long
Content-Type: application/json
{"status":414,"error":"URI Too Long"}4xx Client Error: The request contains an error or can't be fulfilled — fix the request before retrying. See the full list of HTTP status codes.
Related status codes
- 413 Content Too LargeThe request body is larger than the server is willing to accept.
- 431 Request Header Fields Too LargeThe server refuses the request because a header — or all headers together — is too large.
- 400 Bad RequestThe server can't process the request because it's malformed or invalid.
Related tools
Frequently asked questions
What does HTTP 414 URI Too Long mean?
The URL is longer than the server is willing to interpret.
Is 414 a client or a server error?
414 is a 4xx code, so it signals a problem with the request (as seen by the server). Retrying the identical request usually gives the same result.
Where is 414 defined?
In RFC 9110 §15.5.15. It's listed in the IANA HTTP Status Code Registry.
How can I test how my app handles a 414?
Call https://mockfox.dev/api/status/414 — it responds with 414 to any method, with CORS enabled. Add ?delay=2000 to simulate a slow response.