mirror of
https://github.com/rmaake1/httpstatuses.git
synced 2024-09-04 08:39:45 +02:00
1.5 KiB
1.5 KiB
set | code | title | references | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
4 | 414 | Request-URI Too Long |
|
The server is refusing to service the request because the request-target1 is longer than the server is willing to interpret.
This rare condition is only likely to 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 "black hole" of redirection (e.g., a redirected URI prefix that points to a suffix of itself) or when the server is under attack by a client attempting to exploit potential security holes.
A 414 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls 2.
- 1 Content Negotiation RFC7230 Section 5.3
- 2 Calculating Heuristic Freshness RFC7234 Section 4.2.2]3
- Source: RFC7231 Section 6.5.12