<?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: WP Canonical URLs &#8211; the server is redirecting the request in a way that will never complete</title>
	<atom:link href="http://www.locallytype.com/2008/12/31/wp-canonical-urls-the-server-is-redirecting-the-request-in-a-way-that-will-never-complete/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.locallytype.com/2008/12/31/wp-canonical-urls-the-server-is-redirecting-the-request-in-a-way-that-will-never-complete/</link>
	<description>Frank's thoughts about Search, Social Media + Random Bits &#38; Rants</description>
	<lastBuildDate>Wed, 25 Aug 2010 11:53:37 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jason</title>
		<link>http://www.locallytype.com/2008/12/31/wp-canonical-urls-the-server-is-redirecting-the-request-in-a-way-that-will-never-complete/comment-page-1/#comment-106741</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Thu, 11 Feb 2010 05:08:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.locallytype.com/2008/12/31/wp-canonical-urls-the-server-is-redirecting-the-request-in-a-way-that-will-never-complete/#comment-106741</guid>
		<description>For us, it was as simple as going to the blog settings, and changing the default URL, which in our case, was set to the non-www version of the site. This caused us a good chuckle when we found this. After this was reset, the connections were perfect.</description>
		<content:encoded><![CDATA[<p>For us, it was as simple as going to the blog settings, and changing the default URL, which in our case, was set to the non-www version of the site. This caused us a good chuckle when we found this. After this was reset, the connections were perfect.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin</title>
		<link>http://www.locallytype.com/2008/12/31/wp-canonical-urls-the-server-is-redirecting-the-request-in-a-way-that-will-never-complete/comment-page-1/#comment-104662</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Fri, 18 Dec 2009 13:37:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.locallytype.com/2008/12/31/wp-canonical-urls-the-server-is-redirecting-the-request-in-a-way-that-will-never-complete/#comment-104662</guid>
		<description>Really appreciate this, helped me without having to mess with the htaccess file which I could not find.</description>
		<content:encoded><![CDATA[<p>Really appreciate this, helped me without having to mess with the htaccess file which I could not find.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Manuel</title>
		<link>http://www.locallytype.com/2008/12/31/wp-canonical-urls-the-server-is-redirecting-the-request-in-a-way-that-will-never-complete/comment-page-1/#comment-103128</link>
		<dc:creator>Manuel</dc:creator>
		<pubDate>Tue, 11 Aug 2009 22:21:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.locallytype.com/2008/12/31/wp-canonical-urls-the-server-is-redirecting-the-request-in-a-way-that-will-never-complete/#comment-103128</guid>
		<description>Thank you, it was of great usefulness</description>
		<content:encoded><![CDATA[<p>Thank you, it was of great usefulness</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pm</title>
		<link>http://www.locallytype.com/2008/12/31/wp-canonical-urls-the-server-is-redirecting-the-request-in-a-way-that-will-never-complete/comment-page-1/#comment-101862</link>
		<dc:creator>pm</dc:creator>
		<pubDate>Thu, 30 Apr 2009 05:38:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.locallytype.com/2008/12/31/wp-canonical-urls-the-server-is-redirecting-the-request-in-a-way-that-will-never-complete/#comment-101862</guid>
		<description>What if the timeout is soo bad you can&#039;t even log into WordPress to do step 3:
Go to the Plugins Page and activate it.

How can I activate a plug-in if it times-out &amp; I can&#039;t even log in?  The issues is the .htaccess file uses rewrite, rewriting all requests to port 83, and that is the only way PHP will work on this linux vhost server.</description>
		<content:encoded><![CDATA[<p>What if the timeout is soo bad you can&#8217;t even log into WordPress to do step 3:<br />
Go to the Plugins Page and activate it.</p>
<p>How can I activate a plug-in if it times-out &amp; I can&#8217;t even log in?  The issues is the .htaccess file uses rewrite, rewriting all requests to port 83, and that is the only way PHP will work on this linux vhost server.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Calvin Loh</title>
		<link>http://www.locallytype.com/2008/12/31/wp-canonical-urls-the-server-is-redirecting-the-request-in-a-way-that-will-never-complete/comment-page-1/#comment-100403</link>
		<dc:creator>Calvin Loh</dc:creator>
		<pubDate>Tue, 03 Mar 2009 10:22:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.locallytype.com/2008/12/31/wp-canonical-urls-the-server-is-redirecting-the-request-in-a-way-that-will-never-complete/#comment-100403</guid>
		<description>The plug-in stopped the problem, although it raised an error on activation.

Fortunately, I had accounts on two different hosting providers. My blogs on Host A worked correctly after upgrading to 2.7.1. The failed blog was on Host B. I checked, and realized that the blogs on Host A did not have .htaccess files. 

So I removed this file (.htaccess) from my blog on Host B, and it is working again.

Hope this helps someone.</description>
		<content:encoded><![CDATA[<p>The plug-in stopped the problem, although it raised an error on activation.</p>
<p>Fortunately, I had accounts on two different hosting providers. My blogs on Host A worked correctly after upgrading to 2.7.1. The failed blog was on Host B. I checked, and realized that the blogs on Host A did not have .htaccess files. </p>
<p>So I removed this file (.htaccess) from my blog on Host B, and it is working again.</p>
<p>Hope this helps someone.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
