Forum Moderators: phranque
RewriteEngine on
RewriteCond %{HTTP_REFERER} ^http(s)?://(www\.)?a-bad_proxy.com.*$ [NC,OR]
RewriteCond %{HTTP_REFERER} ^http(s)?://(www\.)?a-bad_proxy.com.*$ [NC]
RewriteRule .* www.google.com [L]
but it doesn't works. I can still using the web proxy www.ciaproxy.com to visit my website.
What's the problem?
Thanks in advance!
[edited by: jdMorgan at 12:51 am (utc) on July 20, 2008]
[edit reason] examplified proxy domain. [/edit]
RewriteRule .* - [F]
Do you have any other working RewriteRules? If not, be aware that there are several 'set-up' directives which you did not show, and which may be required to enable mod_rewrite on your server.
Jim
Order Deny,Allow
Deny from 72.233.47.236
Deny from a-bad_proxy.com
Deny from www.a-bad_proxy.com
But it doesn't work.
What's the problem?
Thanks in advance!
[edited by: jdMorgan at 12:52 am (utc) on July 20, 2008]
[edit reason] obscured proxy domain. [/edit]
Whats the reason you wish to block them?
If so then as soon as you block that proxy there move on to the next. There are solutions but they are very time consumming to set up and they do little more than prevent proxies copying content or hijacking. In other words they offer "no pay back". Half the problem is people that suffer this are too whitehat so lets put a greyhat on instead.
Ok instead of banning redirect them to a tarpit. This will use up all there resources and leave them with a wacking great bandwidth bill at then end of the month.
It'd be a great idea, if you weren't with them in the tarpit, also keeping resources on your server busy. and same story for the bandwidth-bill. Also, I've noticed that quite a few of these web-proxy-sites are "deactivated due to billing issues" sooner or later. Thus, the only one that really pays a bill is you.
But in general, I agree, if you just ban them, they might use the next proxy to scrape your site. You could silently rewrite their requests to some dummy-page that does not have your original content on it.