HTTP status code

HTTP 414 URI Too Long

414 URI Too Long means the requested URL is longer than the server is willing to process.

Reviewed: 6 November 2026
Class
4xx · Client errors
Where the problem is
Problem with the request (client)
Who fixes it
You can often fix it yourself (URL, sign-in, cookies).

What it means

Servers and proxies limit URL length (often to a few KB). If a URL exceeds the limit, the server returns a 414. It's often a symptom of another bug, such as a loop that appends a parameter on every redirect.

Most common causes

  • A redirect loop that keeps repeating parameters (e.g. ?redirect=…?redirect=…).
  • A form with lots of data sent via GET instead of POST.
  • Very long tracking parameters or encoded data in the URL.

What you can do as a visitor

  1. Open the site's homepage and find the content again, without the long URL.
  2. Clear the site's cookies if redirects keep sending you round in circles.

Shows the HTTP status, redirect chain, HTTPS and basic SEO signals. Works for public addresses only.

What the site owner or developer should do

  1. Find the redirect loop that keeps lengthening the URL.
  2. Send larger payloads via POST in the request body.
  3. If needed, increase large_client_header_buffers (Nginx) or LimitRequestLine (Apache).

Impact on SEO and Google

Googlebot rarely hits a 414; when it does, it usually points to a loop or broken parameters in internal links.

Frequently asked questions

How long can a URL be?

There's no single limit; most servers allow a few thousand characters. To be safe, stay under about 2,000.

Does a 414 mean a server error?

No. The request is too long, so the source of the URL needs fixing.

Sources