Re: Handling 413 Errors with ProxyPass

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 one generating the 413, but we have a specific error
> document on the backend that's shown to the user when the 413 error
> occurs:
> 
>     (This is still a configuration line from the Apache proxy)
>     ErrorDocument 413 /ErrFileTooLarge

You mean /ErrFileTooLarge is itself a request that is proxied?
I can see how that would recurse: your error document is
configured to reject the request for exactly the same reason
as the original request.  But this is off the top of my head:
I haven't tried to reproduce it.

-- 
Nick Kew



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx




[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux