<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Forcing FAVICON.ICO to appear on the browser address bar</title>
	<atom:link href="http://technologytales.com/2007/06/23/forcing-faviconico-to-appear-on-the-browser-address-bar/feed/" rel="self" type="application/rss+xml" />
	<link>http://technologytales.com/2007/06/23/forcing-faviconico-to-appear-on-the-browser-address-bar/</link>
	<description>Adventures in the world of digital and computer technology</description>
	<lastBuildDate>Tue, 03 Aug 2010 18:45:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: TechnologyTales.com &#124; An unexpected side effect</title>
		<link>http://technologytales.com/2007/06/23/forcing-faviconico-to-appear-on-the-browser-address-bar/comment-page-1/#comment-11</link>
		<dc:creator>TechnologyTales.com &#124; An unexpected side effect</dc:creator>
		<pubDate>Wed, 26 Sep 2007 20:03:32 +0000</pubDate>
		<guid isPermaLink="false">http://technologytales.com/2007/06/23/forcing-faviconico-to-appear-on-the-browser-address-bar/#comment-11</guid>
		<description>[...] I recently posted about using mod_rewrite to block access to your images from all but the websites to which you want access to be available. Following so doing, I discovered that my FAVICON had disappeared from Firefox&#8217;s address. As it turned out, it was easy to fix and that is covered in another recent post. [...]</description>
		<content:encoded><![CDATA[<p>[...] I recently posted about using mod_rewrite to block access to your images from all but the websites to which you want access to be available. Following so doing, I discovered that my FAVICON had disappeared from Firefox&#8217;s address. As it turned out, it was easy to fix and that is covered in another recent post. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
