HTTP 414 URI Too Long

What does HTTP 414 mean?

The URL is longer than the server is willing to process. Servers usually limit URLs to around 8 KB. Very long query strings — huge filter combinations, data stuffed into GET parameters or redirect loops that keep appending parameters — trigger it.

4xx Client error: The request has a problem the client can fix: wrong URL, missing credentials, bad data or too many requests.

Common causes of a 414 error

• Too much data in query parameters.
• A redirect loop that appends to the URL.

How to fix 414 URI Too Long

• Send large data in a POST body instead.
• Fix redirect loops.

414 and SEO

Long, parameter-heavy URLs are also bad for crawling; keep URLs short and canonical.

Example response

HTTP/1.1 414 URI Too Long

How to return a 414 response

Node.js (Express)

res.status(414).json({ error: 'URI Too Long' });

PHP

http_response_code(414);

Python (Flask)

return {'error': 'URI Too Long'}, 414

Go (net/http)

w.WriteHeader(414)

nginx

return 414;

Related status codes

• 413 Content Too Large — The request body is larger than the server allows.
• 400 Bad Request — The server cannot process the request because it is malformed.
• 431 Request Header Fields Too Large — The request headers, or a single header, are too large.

Check which status code a URL returns with the HTTP header checker.