www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Slemko <ma...@znep.com>
Subject Re: general/5974: The requested URL's length exceeds the capacity limit for this server.
Date Sun, 09 Apr 2000 20:20:01 GMT
The following reply was made to PR general/5974; it has been noted by GNATS.

From: Marc Slemko <marcs@znep.com>
To: John Salinas <jsalinas@eden2.net>
Cc: submit@bugz.apache.org
Subject: Re: general/5974: The requested URL's length exceeds the capacity
 limit for this server.
Date: Sun, 9 Apr 2000 14:13:43 -0600 (MDT)

 On 9 Apr 2000, John Salinas wrote:
 > uname -a Linux garden.eden2.net 2.2.12-20 #1 Mon Sep 27 10:40:35 EDT 1999 i686 unknown
 > 
 > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/spec
 > >Description:
 > When I try to access a cgi-bin or <A HREF> 3-4 levels down I receive
 > the following message:
 > Request-URI Too Large
 > 
 > The requested URL's length exceeds the capacity limit for this server.
 > 
 > request failed: URI too long
 > 
 > 
 > Apache/1.3.9 Server at eden2.net Port 80
 > 
 > The log says: [Sun Apr  9 14:33:47 2000] [error] [client 127.0.0.1] request failed:
URI too long
 > [Sun Apr  9 14:34:46 2000] [error] [client 127.0.0.1] request failed: URI too long
 > [Sun Apr  9 14:45:52 2000] [error] [client 127.0.0.1] request failed: URI too long
 
 See:
 
 	http://www.apache.org/docs/mod/core.html#limitrequestline
 
 However, unless you have manually decresed this limit, then your code is
 doing something pretty silly to generate URIs >8000 chars.  Make sure that
 it is not using GET when it should be using POST.  Many clients, proxies,
 and servers don't support insanely long URIs.
 

Mime
View raw message