httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: [users@httpd] ErrorDocument not working for HTTP code 413
Date Tue, 04 Mar 2008 02:58:32 GMT

Since i need to limit the file size being uploaded either via Apache/httpd
or the plugin, i tried using the Apache LimitRequestBody attribute.
I noticed that when this kicks in, though i see an error in the Apache
error log saying that the file size is larger than that is allowed,
this does not result in Error 413 in the access log and nor does the
ErrorDocument kick in.
Was wondering why this would be the case?

"Requested content-length of 1000000801 is larger than the configured limit
of 1000000000, "


"Joshua Slive" <> wrote on 03/03/2008 12:56:52 PM:

> On Mon, Mar 3, 2008 at 3:44 PM,  <> wrote:
> > Joshua,
> >
> >
> >  > Is the 413 returned because you exceed the LimitRequestSize
> >  > for apache?
> >  >
> >
> >  I am not using the Apache parameter but a WLS plugin parameter.
> >  I have set the MaxPostSize parameter within the WLS Apache plugin. I
> >  assuming this causes the 413 to return.
> Well, that's a different story. Apache uses ErrorDocument only when it
> generates the error message itself. It will not override
> application-specific error messages (since this would often result in
> less-useful error messages). The one exception, as Nils points out, is
> that Apache can be configured to override back-end errors when using
> mod_proxy. Your plugin probably doesn't provide that capability.
> >  But if i attempt to upload a much larger file, say 600MB, i get
> >  response in the browser:
> >
> >  The connection was reset
> That's an entirely different story again. Something along the way is
> yanking out the network connection.
> Joshua.

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message