<?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/"
	xmlns:go='http://ns.gigaom.com/'
xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Why Not to Use Google Web Accelerator</title>
	<atom:link href="http://gigaom.com/2005/10/24/why-not-to-use-google-web-accelerator/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2005/10/24/why-not-to-use-google-web-accelerator/</link>
	<description></description>
	<lastBuildDate>Fri, 10 Feb 2012 23:37:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Nik Cubrilovic</title>
		<link>http://gigaom.com/2005/10/24/why-not-to-use-google-web-accelerator/#comment-109640</link>
		<dc:creator><![CDATA[Nik Cubrilovic]]></dc:creator>
		<pubDate>Tue, 25 Oct 2005 06:28:16 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.wordpress.com/2005/10/24/why-not-to-use-google-web-accelerator/#comment-109640</guid>
		<description><![CDATA[Hey Om, there is probably a security hole in there somewhere. The reason why it does cache is so that it can do pre-fetches on sites that wouldn&#039;t otherwise work without cookies (and pre-fetching on sites like amazon without cookies is pointless). In regards to the controversy when GWA was released about it &#039;breaking&#039; sites, I am firmly in the camp that it was the fault of the site developers:

&lt;a href=&quot;http://www.nik.com.au/archives/2005/05/07/poor-web-applications-and-pre-fetch-security-issues/&quot; rel=&quot;nofollow&quot;&gt;GWA and pre-fetch security issues&lt;/a&gt;

ps. love the new design]]></description>
		<content:encoded><![CDATA[<p>Hey Om, there is probably a security hole in there somewhere. The reason why it does cache is so that it can do pre-fetches on sites that wouldn&#8217;t otherwise work without cookies (and pre-fetching on sites like amazon without cookies is pointless). In regards to the controversy when GWA was released about it &#8216;breaking&#8217; sites, I am firmly in the camp that it was the fault of the site developers:</p>
<p><a href="http://www.nik.com.au/archives/2005/05/07/poor-web-applications-and-pre-fetch-security-issues/" rel="nofollow">GWA and pre-fetch security issues</a></p>
<p>ps. love the new design</p>
]]></content:encoded>
	</item>
</channel>
</rss>

