<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Image Leeches</title>
	<atom:link href="http://outerlevel.com/blog/2006/06/06/image-leeches/feed/" rel="self" type="application/rss+xml" />
	<link>http://outerlevel.com/blog/2006/06/06/image-leeches/</link>
	<description>Building a MicroISV</description>
	<pubDate>Tue, 06 Jan 2009 06:27:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Jon Trainer</title>
		<link>http://outerlevel.com/blog/2006/06/06/image-leeches/#comment-603</link>
		<dc:creator>Jon Trainer</dc:creator>
		<pubDate>Wed, 07 Jun 2006 21:43:47 +0000</pubDate>
		<guid isPermaLink="false">http://outerlevel.com/blog/2006/06/06/image-leeches/#comment-603</guid>
		<description>Thanks Rob!  This tutorial and your suggestions will definitely help.</description>
		<content:encoded><![CDATA[<p>Thanks Rob!  This tutorial and your suggestions will definitely help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Drimmie</title>
		<link>http://outerlevel.com/blog/2006/06/06/image-leeches/#comment-602</link>
		<dc:creator>Rob Drimmie</dc:creator>
		<pubDate>Wed, 07 Jun 2006 18:22:51 +0000</pubDate>
		<guid isPermaLink="false">http://outerlevel.com/blog/2006/06/06/image-leeches/#comment-602</guid>
		<description>A really common solution for this is to use .htaccess (I'm sure there's an IIS equivalent) to only allow requests that are referred by your domain's url access to the image.

When you inline an image, that reference acts as a referral to the image file, so outerlevel.com is referring me to http://outerlevel.com/blog/images/bullfrog128.png.

In the same vein, MySpace.com is referring browsers to those two image files.  You can use this knowledge perhaps to block MySpace itself, or (and this is the more common version), to block everything that isn't outerlevel.com or one of your other domains.

There's a reasonably decent tutorial at: http://altlab.com/htaccess_tutorial.html

This is a very common solution.  You can block the image completely, or replace it with a simple, very small image that says "This person inlined an image from outerlevel.com.  How rude!".  Many sites get much much ruder with the replacement images.  One I saw recently that was fairly clever was an image that was a few thousand pixels wide, which fairly severly broke most layouts.

googling ".htaccess image" will turn up lots of other examples and tutorials on how it's done.</description>
		<content:encoded><![CDATA[<p>A really common solution for this is to use .htaccess (I&#8217;m sure there&#8217;s an IIS equivalent) to only allow requests that are referred by your domain&#8217;s url access to the image.</p>
<p>When you inline an image, that reference acts as a referral to the image file, so outerlevel.com is referring me to <a href="http://outerlevel.com/blog/images/bullfrog128.png" rel="nofollow">http://outerlevel.com/blog/images/bullfrog128.png</a>.</p>
<p>In the same vein, MySpace.com is referring browsers to those two image files.  You can use this knowledge perhaps to block MySpace itself, or (and this is the more common version), to block everything that isn&#8217;t outerlevel.com or one of your other domains.</p>
<p>There&#8217;s a reasonably decent tutorial at: <a href="http://altlab.com/htaccess_tutorial.html" rel="nofollow">http://altlab.com/htaccess_tutorial.html</a></p>
<p>This is a very common solution.  You can block the image completely, or replace it with a simple, very small image that says &#8220;This person inlined an image from outerlevel.com.  How rude!&#8221;.  Many sites get much much ruder with the replacement images.  One I saw recently that was fairly clever was an image that was a few thousand pixels wide, which fairly severly broke most layouts.</p>
<p>googling &#8220;.htaccess image&#8221; will turn up lots of other examples and tutorials on how it&#8217;s done.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
