Comments on: Tech: How to prevent image leeching (hot linking) in IIS 6.0

By: Some Guy

Some Guy — Thu, 06 Oct 2011 12:21:57 +0000

Or you can just replace image with something disgusting or damaging stealer’s reputation. He will learn his lesson.

By: Gil

Gil — Sat, 02 May 2009 20:02:49 +0000

One thing I didn’t succeed in doing is add another website (as I run two websites who use the same image folder). I tried to duplicate the following line:
RewriteCond %{HTTP_REFERER} ^(?!http?://(?:www\.)website1\.com/) [I]
RewriteCond %{HTTP_REFERER} ^(?!http?://(?:www\.)website2\.com/) [I]

But it didn’t work. Any idea?

By: Gil

Gil — Sat, 02 May 2009 19:51:32 +0000

Worked great for me.

One thing I would add: Another way to find who is leeching on you, is to put the following search string in Google Images:
site:www.yoursite.com

This will pick up the images on your website, whether linked from your website or from leeches.

All the best!
Gil

By: mike

mike — Tue, 10 Mar 2009 15:48:45 +0000

Hi Dennis,

Yes, replace “yoursite” with your domain.

Best,

Mike

By: Dennis Nyhagen

Dennis Nyhagen — Tue, 10 Mar 2009 15:43:28 +0000

I’m assuming where it says yoursite in the code that we insert our domain name?

Thanks in advance.

By: mike

mike — Thu, 19 Feb 2009 20:34:11 +0000

Hello Guy,

That’s very interesting. I’ve had quite a few links to this article from across the internet from people who reckon it does work. You say it works intermittently, which might indicate some sort of IIS failure sequence (fail/restart), but without a log file I cannot say.

Best of luck with getting your ISAPI rewrite working.

Best,

Mike

By: Guy

Guy — Thu, 19 Feb 2009 20:31:23 +0000

I spent a day trying to get this to work without success.
Worked intermittently but ultimately couldnt get it to stop hotlinking