At 20:11 27.11.2002, Ernest E Vogelsinger spoke out and said: --------------------[snip]-------------------- >Ooops - you should normally only get this with GET requests where the max. >query string size is exceeded - I'd check the Apache docs though... seems >positively to be connected to the web server. --------------------[snip]--------------------
wrong. From RFC2616 (http://ftp.rfc-editor.org/in-notes/rfc2616.txt): 10.4.14 413 Request Entity Too Large The server is refusing to process a request because the request entity is larger than the server is willing or able to process. The server MAY close the connection to prevent the client from continuing the request. If the condition is temporary, the server SHOULD include a Retry- After header field to indicate that it is temporary and after what time the client MAY try again. 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. Error 413 certainly denotes that the web server refuses to handle the request. No idea how to configure this value but I'm sure it can be done with Apache. I see a better chance of getting this answere on the apache mailing list. -- >O Ernest E. Vogelsinger (\) ICQ #13394035 ^ http://www.vogelsinger.at/
