4144xx
4xx — Client Error
URI Too Long
The URI requested by the client is longer than the server is willing to interpret.
What it means
The HTTP 414 URI Too Long response status code indicates that the URI requested by the client is longer than the server is willing to interpret.
There are a few rare conditions when this might occur: when a client has improperly converted a POST request to a GET request with long query information, when the client has descended into a loop of redirection, or when the server is under attack.
How it works
- 1The client sends a GET request with an incredibly long query string (e.g. 10,000 characters).
- 2The server's HTTP parser hits its configured URL length limit.
- 3The server returns 414 and drops the connection.
Why you're seeing this
- • Sending too much data in a GET query string.
How to fix it
- • Convert the request to a POST and move the massive data payload into the request body, which has much higher limits.
Framework Implementations
Nginx
server {
large_client_header_buffers 4 16k; # Increase max URI length to 16KB
}Real-Life Scenarios
Servers handle this automatically to prevent buffer overflow attacks. You shouldn't need to throw this in your application code.
Massive GET Filters
A frontend tries to send 500 product IDs in a GET query string: /api/products?id=1&id=2&... The URL exceeds 8KB, and Nginx returns 414.
HTTP Transaction
1. Client Request
GET /search?q=a...[10000 chars]...z HTTP/1.1
2. Server Response
HTTP/1.1 414 URI Too Long Content-Type: text/html <h1>Request-URI Too Long</h1>
SEO Implications
None.