View Single Post
Old 2008-02-11, 11:16 AM   #7
cd34
a.k.a. Sparky
 
cd34's Avatar
 
Join Date: Sep 2004
Location: West Palm Beach, FL, USA
Posts: 2,396
Two things:

deny from reverse.gdsz.cncnet.net
deny from gdsz.cncnet.net

Having that in your .htaccess is going to cause apache to have to do a reverse dns lookup for each visitor to your web page. If there is no reverse dns, or, an improperly configured DNS entry, or a timeout on the reverse lookup, any surfer hitting the page will take time to resolve that before they are allowed access.

Secondly -- are you saying that those webservers/IPs are the ones hittin your site? or, is it actually a referring site that is sending surfers/bots?

Code:
x.x.x.x - - [11/Feb/2008:06:32:18 -0500] "GET /images/xxxxxxx.jpg HTTP/1.1" 200 9128 "http://www.blahblah.com" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; SIMBAR={4194A8CC-7C68-11DD-956D-000D6112ED67}; .NET CLR 2.0.50727)"
So, are the entries you're seeing corresponding with the x.x.x.x in the above log line, or "http://www.blahblah.com"

If "http://www.blahblah.com", then you need something like:

Code:
RewriteEngine on
RewriteCond %{HTTP_REFERER} reverse.gdsz.cncnet.net [NC]
RewriteRule .* - [F,L]
Based on your original post, I'm thinking you're probably wanting to ban hits coming from that referrer rather than the domain.
__________________
SnapReplay.com a different way to share photos - iPhone & Android
cd34 is offline   Reply With Quote