Skip to the content

414 URI Too Long

The address of the request is longer than the server is willing to handle. Usually too much data ended up in the query string.

Class
4xx Client error. The request is the problem: a wrong address, missing credentials, data the server can't accept.
Defined in
RFC 9110
Also known as
Request-URI Too Long

Share this tool:TwitterFacebookLinkedInWhatsAppEmail

What causes it

When a URL exceeds the limit of the server, which is about 8,000 characters by default in both nginx and Apache. It happens when a form with a lot of data is sent with GET, when a long list of ids is put in the query string, or when a redirect loop adds a parameter on every round.

What to do about it

Move the data out of the address and send it in the body of a POST. If the long URL is the result of a redirect, look for the loop. The limit can be raised (LimitRequestLine in Apache, large_client_header_buffers in nginx), but browsers, proxies and CDNs have limits of their own, so a short address is the safer fix.

Not to be confused with

413 Content Too LargeThe body is too large.
431 Request Header Fields Too LargeThe headers are too large.

All codes are on the list of HTTP status codes, which can be searched by number and by word.

See all 12