I set a throttle policy of maximum 50 requests per ip per second. The idea is to stop harvesters.. not regular users. Hopefully 50 should be a good balance.. if anyone is seeing problems accessing this site, please let me know?. The idea is to limit site usage to harvesters and scripts, not regular users..
mod_throttle has incredibly dense documenation.. had to read it several times to understand what needed to be done.. and I'm not all that slow.
Here's my config:
In the Server configuration section of apache:
<IfModule mod_throttle.c>
ThrottleClientIP 100
</IfModule>
Which essentially says: Throttle per client IP, keep a history of 100. 100 should be more than enough for my site, since my average requests per hour is 80-90. Too long of a history and it'll be a burden on system resources.
In the virtual host configuration section:
<IfModule mod_throttle.c>
ThrottlePolicy Request 50 1
</IfModule>
In plain English: limit requests to 50 per IP address per second. I had it initially set to 20 but found that to be too low.. a very busy page (like MT's config panel) wouldn't load completely.. that's bad.
Now since this is my first time configuring mod_throttle and documentation is rather dense and information online very limited I may find out I'm doing something incredibly stupid here.. I guess I'll have to wait and see :)
TrackBack URL for this entry: http://www.unix-girl.com/mt/mt-tb.cgi/119
Do robots hit at that fast a rate? I sometimes get an occasional script that runs through the alphabet soup of MSFT vulnerability scans rapidly, but I can't think of any instance above 50/sec.
A request for a page can consist of a lot more requests depending on how complex the page is..
My main blog page currently is 4.. main page, stylesheet, xml graphic and my cute little daisies there...
#