mod_ratelimit design mistake
https://httpd.apache.org/docs/trunk/mod/mod_ratelimit.html Provides a filter named RATE_LIMIT to limit client bandwidth. The connection speed to be simulated is specified, in KiB/s compared with external mod_bw.so IMHO this is a design mistake * saying i have several virtual hosts * my line has a capacity of 512 KB/Sec * one of the virtual hosts starts to have high traffic and abuses my upstream * SetEnv rate-limit 256 limits each client to 256 KB/sec at it's own * two of them abuse my upstream completly __ http://bwmod.sourceforge.net http://mariusvw.com/tag/mod_bw/ would limit the one vhost to 256 KB/sec. meaning in the case of 3 connections each would get 85 KB/sec. and the half of my available bandwidth is for other vhosts there is another interesting implementation detail of mod_bw LargeFileLimit * 500 786432 would only limit the bandwidth of files larger than 500 KB what is perfect in many cases to prevent line-overload by large downloads while respond with full performance to normal website-requests to serve small requests as quick as possible and prevnbt run out of workers IfModule mod_bw.c BandWidthModule On ForceBandWidthModule On LargeFileLimit * 500 786432 /IfModule signature.asc Description: OpenPGP digital signature
Re: mod_ratelimit design mistake
On Fri, May 10, 2013 at 4:11 PM, Reindl Harald h.rei...@thelounge.net wrote: https://httpd.apache.org/docs/trunk/mod/mod_ratelimit.html Provides a filter named RATE_LIMIT to limit client bandwidth. The connection speed to be simulated is specified, in KiB/s compared with external mod_bw.so IMHO this is a design mistake * saying i have several virtual hosts * my line has a capacity of 512 KB/Sec * one of the virtual hosts starts to have high traffic and abuses my upstream * SetEnv rate-limit 256 limits each client to 256 KB/sec at it's own * two of them abuse my upstream completly It sounds more useful, and far more complicated, to limit the overall bandwdith. But mod_ratelimit does what it says. It's not fair to say whoever wrote it should have instead scratched the itch described above.
Re: mod_ratelimit design mistake
Am 10.05.2013 22:38, schrieb Eric Covener: On Fri, May 10, 2013 at 4:11 PM, Reindl Harald h.rei...@thelounge.net wrote: https://httpd.apache.org/docs/trunk/mod/mod_ratelimit.html Provides a filter named RATE_LIMIT to limit client bandwidth. The connection speed to be simulated is specified, in KiB/s compared with external mod_bw.so IMHO this is a design mistake * saying i have several virtual hosts * my line has a capacity of 512 KB/Sec * one of the virtual hosts starts to have high traffic and abuses my upstream * SetEnv rate-limit 256 limits each client to 256 KB/sec at it's own * two of them abuse my upstream completly It sounds more useful, and far more complicated, to limit the overall bandwdith. but possible and mod_bw did it at least 5 years ago But mod_ratelimit does what it says It's not fair to say whoever wrote it should have instead scratched the itch described above this was not meant as attack i only was wondering by try to replace as most 3rd party modules as possible with the capabilites of Apache 2.4 like mod_remoteip for mod_rpaf does perfectly that mod_ratelimit will not fit currently it's not hardly needed here because faster line but in the times with DSL lines mod_bw did save more than once signature.asc Description: OpenPGP digital signature
