414 Request-URI Too Large
The URL is longer than the server accepts
Seen in nginx, Apache, APIs
The request line, mostly the query string, is too long for the server to accept (the current name is 414 URI Too Long).
Common causes
- Large amounts of data sent as GET query parameters.
- A redirect loop that appends to the query string each time.
- Long tracking or filter parameters built up by the client.
How to fix it
- Send large data in a POST body instead of the URL.
- Fix redirects that keep adding parameters.
- If long URLs are genuinely needed, raise large_client_header_buffers in nginx or LimitRequestLine in Apache.
Got a different message? Paste it into the error explainer.
Related errors
- 502 Bad Gateway · The proxy got a bad response from the server behind it
- 504 Gateway Timeout · The server behind the proxy took too long
- Error 520: Web server is returning an unknown error · Cloudflare got an empty or invalid response
- 429 Too Many Requests · You've hit a rate limit
- 400 Bad Request · The server could not understand the request
- 401 Unauthorized · The request needs valid credentials
- 403 Forbidden · The server refuses to allow this request
- 404 Not Found · Nothing exists at this URL
- 405 Method Not Allowed · This URL does not accept that HTTP method
- 410 Gone · The resource was removed on purpose
- 500 Internal Server Error · The application hit an error it did not handle
- 400 Bad Request: The plain HTTP request was sent to HTTPS port · Plain HTTP was sent to a port that expects TLS