Isn't this considered to be a DOS (denial of service) attack, where the attacker takes down a site by pinging it to death and eating up it's bandwidth? I think there are programs floating around that a person can use to do just that in an automated manner.
Can you contact their provider and get them shut down for this?
A few years ago I used to have the same problem then I removed the page where that particular visitor was directed to and that was it.
They get a 404 page not found, instead of running around in circles from trying to access a real page and being redirected each time.
edited: opps Staffa already said what I wrote. That error page you have could possibly add fuel to the fire.
You could always redirect the .htaccess denial to go to www.yahoo.com, or [127.0.0.1...] (i.e. his own PC).
Thanks guys...I guess the reason we have a "banned" page in the first place is that so many sites recommend it...I had considered re-directing them to another site, but that's not a good idea, because the page is displayed anytime someone tried to access a forbidden folder or part of the site. Just because someone tries to do that, they shouldn't be sent to yahoo...
Be careful that the IP addresses you ban are listed in ARIN, RIPE, APNIC, etc. as "Assigned Permanent" addresses. If not, then you may be banning IP addresses within a pool shared by dial-up users (for example) and you may be banning legitimate visitors.
If you really need to ban shared dial-up IPs, then it's best to limit the ban to an hour or so, rather than making it permanent. This will also help to keep your banned IP list from becoming riduculously large over time.
Consider having a dynamic ban list -- it works for me.
Rather than having any sites in a manual list for band-width abuse, a CGI routine checks if the IP address is requesting too fast.
If so, they get a banned page. Bans last from 5 minutes to 24 hours depending on how heavily they've been hitting us. Repeated bans tend to be longer.
Usually stops the most rampaging, out of control, spider in less time than it takes me to check the logs.
1 example (of about 10 cases) from just today where the kid accessed the page repeatedly for 40 minutes:
How many times total in that 40 minutes?
You might look into mod_throttle as a way to deal with too many requests from the same ip.
Also instead of a banned page you can just serve a blank page (i.e. serve a file blank.html which is totally empty) or forbid them in .htaccess Look around the forums ... there are some good .htaccess discussions involving blocking/forbiding/redirecting these sorts of folks.