2015-11-06 21:39:33 +01:00
---
set: 4
code: 414
title: Request-URI Too Long
2015-11-07 05:34:40 +01:00
references:
"Rails HTTP Status Symbol": ":request_uri_too_long"
2016-01-27 23:08:33 +01:00
"Go HTTP Status Constant": "http.StatusRequestURITooLong"
2016-04-19 15:19:17 +02:00
"Symfony HTTP Status Constant": "Response::HTTP_REQUEST_URI_TOO_LONG"
2015-11-06 21:39:33 +01:00
---
2016-04-23 02:12:07 +02:00
The server is refusing to service the request because the request-target< sup > [1](#ref-1)< / sup > is longer than the server is willing to interpret.
2015-11-07 06:45:46 +01:00
2016-04-23 02:12:07 +02:00
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.
2015-11-07 05:34:40 +01:00
2016-04-23 02:12:07 +02:00
A 414 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls < sup > [2](#ref-2)< / sup > .
2015-11-07 05:34:40 +01:00
2015-11-09 02:44:05 +01:00
---
* < span id = "ref-1" >< sup > 1</ sup > Content Negotiation
[RFC7230 Section 5.3][2]< / span >
* < span id = "ref-2" >< sup > 2</ sup > Calculating Heuristic Freshness
RFC7234 Section 4.2.2][3]< / span >
* Source: [RFC7231 Section 6.5.12][1]
2015-11-07 05:34:40 +01:00
[1]: < http: / / tools . ietf . org / html / rfc7231 # section-6 . 5 . 12 >
[2]: < http: / / tools . ietf . org / html / rfc7231 # section-5 . 3 >
2016-01-27 23:08:33 +01:00
[3]: < http: / / tools . ietf . org / html / rfc7234 # section-4 . 2 . 2 >