Request-URI Too Large settings help
mdounin at mdounin.ru
Wed Apr 16 02:01:03 MSD 2008
On Tue, Apr 15, 2008 at 02:32:58PM -0700, rkmr.em at gmail.com wrote:
>I am getting this error:
>Request-URI Too Large
>The requested URL's length exceeds the capacity limit for this server.
>request failed: URI too long
>even with these settings..
> client_header_buffer_size 8k;
> large_client_header_buffers 4 8k;
> fastcgi_buffers 32 4k;
> fastcgi_buffer_size 4k;
>this is the URL that is getting failed.. please help!
[...skipped awfull really long uri, which probably will be just
thrown away by some servers and truncated by others...]
Have you tried using POST method instead? Looks like RFC 2616
mentions your case explicitly:
% 10.4.15 414 Request-URI Too Long
% The server is refusing to service the request because the Request-URI
% 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 URI "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 security holes present in some servers using fixed-length
% buffers for reading or manipulating the Request-URI.
Note the "has improperly converted ..." part.
More information about the nginx