Ok
Thus, the main problem that you are facing is that after the download is completed, the Apache LimitRequestBody or LimitXMLRequestBody directive is applied. It seems that apache is expecting a complete file in a temporary folder before checking the size.
So, you need to disconnect the connection immediately after detecting too large downloads. One of the mod_throttle mods was the module available for this. If you are checking out this alternative to the issue of disabling mod_throttle , you might have a list of bandwidth control modules that can suit your needs.
mod_bwshare , for example, can limit the bandwidth for each IP client, but this is not a limit on every request per IP_. There is also mod_quos that handles a lot of download restrictions, but I can't find many things to control the download (only closing is possible, early slow loading). See also this response to throttle loading .
That way, you can also check the OS level restriction (over the TCP stack) or the advanced firewall (ask about the denial).
You can also use client-side restriction tools, such as hidden form values ββor js loader options, but, like everything that is used on the client side, from a security point of view, you cannot avoid someone changing the restrictions on the side customer.
regilero
source share