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"
|
2015-11-06 21:39:33 +01:00
|
|
|
---
|
|
|
|
|
|
2015-11-07 06:45:46 +01:00
|
|
|
The 414 URI Too Long status code indicates that the server is refusing to
|
2015-11-07 05:34:40 +01:00
|
|
|
service the request because the request-target ([Section 5.3 of RFC7230][2]) is
|
2015-11-07 06:45:46 +01:00
|
|
|
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.
|
2015-11-07 05:34:40 +01:00
|
|
|
|
|
|
|
|
A 414 response is cacheable by default; i.e., unless otherwise indicated by the
|
|
|
|
|
method definition or explicit cache controls
|
|
|
|
|
(see [Section 4.2.2 of RFC7234][3]).
|
|
|
|
|
|
|
|
|
|
Source: [RFC7231 Section 6.5.12][1]
|
|
|
|
|
|
|
|
|
|
[1]: <http://tools.ietf.org/html/rfc7231#section-6.5.12>
|
|
|
|
|
[2]: <http://tools.ietf.org/html/rfc7231#section-5.3>
|
|
|
|
|
[3]: <http://tools.ietf.org/html/rfc7234#section-4.2.2>
|
