What 414 means
The URL (strictly, the request target) is longer than the server will process.
When servers send it
When a request line is longer than the server’s buffer. Different servers and proxies have different limits.
Common causes
- A form using GET with lots of data, putting it all in the query string.
- A redirect loop that keeps adding to the URL each time round.
- Huge filter lists or encoded data (such as base64) in query parameters.
- Tracking parameters piling up through several redirects.
How to fix it as a developer
- Move large data into a POST body.
- Look for a redirect loop that appends parameters.
- Keep URLs under about 2,000 characters to be safe across browsers, servers and CDNs.
- If you control the server, limits are configurable (nginx:
large_client_header_buffers).
How to fix it as a visitor
- Go back to the site’s home page and navigate from there, rather than using a long copied link.
Related codes
- 413 Content Too Large: The request body, such as an upload, is bigger than the server will accept.
- 431 Request Header Fields Too Large: The request headers are too big, very often because of too many or too large cookies.
- 400 Bad Request: The server can’t or won’t handle the request because something in it is malformed.
Where it’s defined
414 URI Too Long is defined in RFC 9110, section 15.5.15. It’s a 4xx code, the client error class: something is wrong with the request, so sending it again unchanged won’t help.
Other 4xx codes
400 Bad Request · 401 Unauthorized · 402 Payment Required · 403 Forbidden · 404 Not Found · 405 Method Not Allowed · 406 Not Acceptable · 408 Request Timeout · 409 Conflict · 410 Gone · 413 Content Too Large · 415 Unsupported Media Type · 418 I’m a teapot · 422 Unprocessable Content · 429 Too Many Requests · 431 Request Header Fields Too Large · 451 Unavailable For Legal Reasons · 499 Client Closed Request
Or search them all in the HTTP status code list.