The first thing to check is if it is an HTTPD error or a Tomcat error. You haven't explicitly said this, but I am guessing you are using HTTPD as a reverse proxy. Check the Tomcat logs first. If the 413 shows up there, it is a problem with Tomcat and not with HTTPD.
Check the HTTPD error log also to make sure the errors are actually in it. It is also possible if there are any upstream proxies (like an office web filter) that one of them is generating the error. If the error is in the HTTPD logs and not in the Tomcat logs, you will probably need to dump the traffic using mod_dumpio or tcpdump and compare a complete and error request (mod_logio will tell you the sizes, but not the contents - you could use it as a starting point if you don't want to dump all the traffic). - Y On Thu, Jul 23, 2015 at 5:04 PM, Cohen, Laurence <lco...@novetta.com> wrote: > Hi everyone, > > We are suddenly having the following problem on several of our servers, > and I have not been able to find a solution on the internet that has > resolved it. Our configuration is the following. > > Apache httpd 2.2.3 running on RHEL5 > Tomcat 7, also running on RHEL5 > > When we try to upload a file bigger than a few megabytes, we get the > following error: > > The requested resource > /dse/submissions/100103040/add_file > does not allow request data with POST requests, or the amount of data > provided in the request exceeds the capacity limit > > I've tried to figure out what the maximum size file is, but the problem > will occur on a file, and then we try the same file a few minutes later and > it works. > > I tried setting LimitRequestBody to 0, which I believe is the default > anyway, but it had no effect either way. > > If anyone has any ideas, please let me know. > > Thanks, > > Larry Cohen > > >
