<?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: Yahoo Develops a Glitch, Interprets https/http wrongly!</title>
	<atom:link href="http://www.pagetraffic.com/seo-blog/yahoo-develops-a-glitch-interprets-httpshttp-wrongly/4594/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pagetraffic.com/seo-blog/yahoo-develops-a-glitch-interprets-httpshttp-wrongly/4594/</link>
	<description>Search engine news, SEO Tips, Google updates, SEO articles</description>
	<lastBuildDate>Tue, 16 Mar 2010 12:42:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: phizm</title>
		<link>http://www.pagetraffic.com/seo-blog/yahoo-develops-a-glitch-interprets-httpshttp-wrongly/4594/comment-page-1/#comment-348653</link>
		<dc:creator>phizm</dc:creator>
		<pubDate>Sun, 18 May 2008 09:23:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.pagetrafficblog.com/yahoo-develops-a-glitch-interprets-httpshttp-wrongly/4594/#comment-348653</guid>
		<description>You have a &#039;glitch&#039; in your article.

The CGI they&#039;re referring to is the &#039;Common Gateway Interface&#039;, a standard for server application interfaces. Computer-Generated Imagery makes no sense in this context.

Just thought I&#039;d point that out to save people confusion.</description>
		<content:encoded><![CDATA[<p>You have a &#039;glitch&#039; in your article.</p>
<p>The CGI they&#039;re referring to is the &#039;Common Gateway Interface&#039;, a standard for server application interfaces. Computer-Generated Imagery makes no sense in this context.</p>
<p>Just thought I&#039;d point that out to save people confusion.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->