HTTP 414 URI Too Long
The request URL (usually the query string) is longer than the server will accept.
URI too longRequest-URI Too LongRequest-URI Too Large Meaning
Servers cap URL length — around 8 KB in Nginx/Apache by default, and browsers/CDNs have their own limits. Long URLs usually come from stuffing data (filters, IDs, base64) into GET parameters or from redirect loops that keep appending parameters.
Common causes
- Large data sent as GET query parameters (long ID lists, JSON, base64)
- Redirect loop appending
?next=or?redirect=repeatedly - Tracking parameters accumulating
- Search/filter UIs encoding all state into the URL
⚡ Quick fix
- Send large payloads in a POST body instead
- Fix redirect loops that keep growing the URL
- Store filter state server-side and pass a short ID
- Raise server limits only as a last resort
Detailed fix by platform
Nginx
- Raise header buffer (URL is part of the request line):nginx
large_client_header_buffers 4 32k;
Apache
LimitRequestLine 16384in the server config (not .htaccess).
How to diagnose
- Length — How long is the URL?
- Content — What is in the query string?
- Loop — Is it growing on each redirect?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in HTTP
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 9 Oct 2026