Skip to content
4xx · Client Error

414 URI Too Long

The requested URL is longer than the server is willing to interpret.

What it means

HTTP 414 URI Too Long means the request's URL exceeds the maximum length the server accepts. Servers cap URL length to protect against buffer overruns and abuse, and a request that blows past the cap is rejected outright.

When it happens

It happens when a form that should use POST is submitted with GET, stuffing a long query string into the URL, or when a request encodes a large amount of data into the URL instead of the body. It can also follow a redirect loop that keeps appending parameters.

How to fix it

  • Switch large requests from GET to POST so the data travels in the body, not the URL.
  • Trim unnecessary query parameters and shorten the URL.
  • Raise the server's URL-length limit (such as large_client_header_buffers in Nginx) only if long URLs are genuinely needed.
  • Check for a redirect loop that is growing the URL on each hop.

SEO impact

Negative if it hits real URLs. A page whose URL is too long to fetch cannot be crawled or indexed, so keep important URLs short and clean.

Check it with Sitewell

Find out which of your URLs return 414

Paste a list of URLs and Sitewell checks the status code of every one at once — free and without signup.

Related codes

Related guides