Re: [users@httpd] Handling 413 Errors with ProxyPass

2017-05-01 Thread Nick Kew
On Mon, 2017-05-01 at 19:17 +0800, Liwei wrote: > > Apache is acting as a proxy with mod_security being used to limit the > maximum request sizes. Aha! Another component in the chain. Do you get the same behaviour if you remove mod_security and use LimitRequestBody instead? > So Apache is the

Re: [users@httpd] Handling 413 Errors with ProxyPass

2017-05-01 Thread Liwei
On 1 May 2017 at 19:17, Liwei wrote: > > Hi Nick, replies inline... > > On Mon, 1 May 2017 at 18:14 Nick Kew wrote: >> >> On Mon, 2017-05-01 at 15:08 +0800, Liwei wrote: >> > Hi list, >> > I'm seeing an unexpected behaviour when a 413 Request Entity Too >> > Large error occurs on a site proxi

Re: [users@httpd] Handling 413 Errors with ProxyPass

2017-05-01 Thread Liwei
Hi Nick, replies inline... On Mon, 1 May 2017 at 18:14 Nick Kew wrote: > On Mon, 2017-05-01 at 15:08 +0800, Liwei wrote: > > Hi list, > > I'm seeing an unexpected behaviour when a 413 Request Entity Too > > Large error occurs on a site proxied with Apache 2.4.25. There is an > > ErrorDocumen

Re: [users@httpd] Handling 413 Errors with ProxyPass

2017-05-01 Thread Nick Kew
On Mon, 2017-05-01 at 15:08 +0800, Liwei wrote: > Hi list, > I'm seeing an unexpected behaviour when a 413 Request Entity Too > Large error occurs on a site proxied with Apache 2.4.25. There is an > ErrorDocument configured for this error but it does not show up as > (from the error page itself

[users@httpd] Handling 413 Errors with ProxyPass

2017-05-01 Thread Liwei
Hi list, I'm seeing an unexpected behaviour when a 413 Request Entity Too Large error occurs on a site proxied with Apache 2.4.25. There is an ErrorDocument configured for this error but it does not show up as (from the error page itself): "Additionally, a 413 Request Entity Too Large error