Forum Moderators: phranque
We desperately are in need to stop referrals to our web site from a handful of locations that have pirated our software. Why they need to come to our site first before the steal - I do not know but in any case, we have tried so many htaccess scripts and nothing seems to work. We ether get a internal server error or, when we don't, the bad sites are still flying in. We are getting slammed with 1000+ visits a day.
Here is the code we used that did not stop them.
1. We are on a Apache server at port 80.
2. I will use 'example' in the names just for this post.
RewriteEngine on
# Options +FollowSymlinks
RewriteCond %{HTTP_REFERER} example123\.com [NC,OR]
RewriteCond %{HTTP_REFERER} example234.blogspot\.com
RewriteCond %{HTTP_REFERER} example345\.ru
RewriteRule .* - [F]
thank you ever so much for any help!
Sara
[edited by: jdMorgan at 8:19 pm (utc) on April 2, 2009]
[edit reason] example.com [/edit]
I tried this since the site anonym site shows how to generate their code but no go. Am I getting warmer or?
So I see nothing hat would have kept at least one of your attempts from working.
If the country-code on the referrer can change, just leave it off and use something like:
RewriteCond %{HTTP_REFERER} anonym\.to [NC,OR]
Jim
Options +FollowSymlinks
#
RewriteCond %{REQUEST_URI} !^/403.shtml
RewriteCond %{HTTP_REFERER} badsite1\.com [NC,OR]
RewriteCond %{HTTP_REFERER} anonym\.to [NC,OR]
RewriteCond %{HTTP_REFERER} badsite2\.com [NC]
RewriteRule .* - [F]
All of the sites (list not shown) are blocked. The anonym\.to is not working.
S
RewriteCond %{REQUEST_URI} !^/403.shtml
RewriteCond %{REMOTE_HOST} anonym\.to [NC,OR]
RewriteRule .* - [F]
CAUSED 500 ERROR BECAUSE OF THE [NC,OR] I ASSUME.
AND
Options +FollowSymlinks
#
RewriteCond %{REQUEST_URI}!^/403.shtml
RewriteCond %{REMOTE_HOST}anonym\.to [NC]
RewriteRule .* - [F]
DID NOT WORK! :-(
Here's some info on this anonym.to
The advantages of anonymizing your external links with anonym.to
Webmasters can use this tool to prevent their site from appearing in the server logs of referred pages as referrer. The operators of the referred pages cannot see where their visitors come from any more.
Using the referrer removal service is quite easy:
http://anonym.to/?http://www.example.com/ produces an anonymous link to example.com which prevents the original site from appearing as a referrer in the logfiles of the referred page.
Again: The link they are using is, http://anonym.to/?http://www.OURSITE.com/nv2009.htm
[edited by: Sara_Page at 2:03 am (utc) on April 16, 2009]
[edited by: jdMorgan at 2:23 am (utc) on April 16, 2009]
[edit reason] example.com [/edit]
Consider putting your protected content behind an authorization script, and requiring either a visit to one of your own site's pages (which sets a short-lived cookie to be checked by the script before it will display the protected content) or you could require visitors to log in before the script will serve protected content.
The basis of the Web is that it is open. It was originally designed for use by academics and government employees. For this reason, many of the foundations of the Web lack restrictive access controls, except by adding additional layers of code on the server.
Jim
Anyway, I will check logs and see if there's any info there that may help. Protection is out there for our type of products but it is very costly and we have seen that hacked too.
Thanks you again!
[edited by: Sara_Page at 2:32 am (utc) on April 16, 2009]