On Fri, Feb 29, 2008 at 9:03 PM, <Ramdas.Hegde@xxxxxxxxxxx> wrote: > > I am using httpd 2.2.4 with BEA Weblogic plug-in for Apache. > I have configured the ErrorDocument to handle HTTP return codes returned by > the app. I have set a MaxPostSize attribute on the WLS plug-in to limit the > file uploads. > When i simulate HTTP status 413 for large file uploads by doing a > multi/form-data post in my browser, though the plug-in/httpd seem to be > returning a HTTP code 413 as is seen in the access log, the ErrorDocument > that i have configured to handle this does not seem to kick in. > The ErrorDocument does work for other configured error codes which means my > webserver configuration is right. > > Under what circumstances would Apache httpd not redirect the browser to > the page specified by ErrorDocument? > > The entry in the access log appears as: > > "POST > /xfer/xfer/Rendezvous/?cm=uf&id=c6ef4300-8675-4c00-b403-71e93284c845&sd=b36cd054c9b151be8d8b5a2b76215924&p=1&rp=&rpo=0&pg=1 > HTTP/1.1" > 413 277 "http://ra-dev.test.com/falcon/addFiles.jsp?p=1&rp=&rpo=0&pg=1"; > "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12) > Gecko/20080201 Firefox/2.0.0.12" Is the 413 returned because you exceed the LimitRequestSize configured for apache? If so, this may be one of those errors that deliberately doesn't invoke custom ErrorDocuments. In the case of errors that may be resource-exhausting attacks by clients, apache short-circuits the normal error handling and returns a hard-coded message. This is because it is considered unsafe to go forward with full request processing when the server may be in a bad state due to resource exhaustion. I'd have to check the code to see if this explains your particular case. See the paragraph near the bottom of http://httpd.apache.org/docs/2.2/mod/core.html#errordocument Joshua. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|