<?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: Redirecting Old WordPress Permalinks to a New Domain</title>
	<atom:link href="http://www.happy-plastic.com/blogging/redirecting-old-wordpress-permalinks-to-a-new-domain/feed" rel="self" type="application/rss+xml" />
	<link>http://www.happy-plastic.com/blogging/redirecting-old-wordpress-permalinks-to-a-new-domain</link>
	<description>Gizmos, Gadgets and Design</description>
	<lastBuildDate>Fri, 23 Apr 2010 05:28:28 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ashleigh</title>
		<link>http://www.happy-plastic.com/blogging/redirecting-old-wordpress-permalinks-to-a-new-domain/comment-page-1#comment-382</link>
		<dc:creator>Ashleigh</dc:creator>
		<pubDate>Sat, 04 Jul 2009 09:16:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.happy-plastic.com/?p=130#comment-382</guid>
		<description>Actually it&#039;s not wrong. It&#039;s dependant on the WordPress installation and the root domain specified. In my case, the / at the end of the domain is inclusive, hence not needing to use it in the 301 redirect.

Thanks for pointing it out though.

To anyone looking at implementing a redirect when moving a blog to a new domain - try both including and leaving out the / to see which works for you.</description>
		<content:encoded><![CDATA[<p>Actually it&#8217;s not wrong. It&#8217;s dependant on the WordPress installation and the root domain specified. In my case, the / at the end of the domain is inclusive, hence not needing to use it in the 301 redirect.</p>
<p>Thanks for pointing it out though.</p>
<p>To anyone looking at implementing a redirect when moving a blog to a new domain &#8211; try both including and leaving out the / to see which works for you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://www.happy-plastic.com/blogging/redirecting-old-wordpress-permalinks-to-a-new-domain/comment-page-1#comment-381</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Mon, 29 Jun 2009 10:38:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.happy-plastic.com/?p=130#comment-381</guid>
		<description>FYI, your 301 code is wrong.

RedirectMatch 301 (.*) http://www.your-domain.com$1 results in broken redirects.

You&#039;re missing a /

RedirectMatch 301 (.*) http://www.your-domain.com/$1 is what you want.</description>
		<content:encoded><![CDATA[<p>FYI, your 301 code is wrong.</p>
<p>RedirectMatch 301 (.*) <a href="http://www.your-domain.com$1" rel="nofollow">http://www.your-domain.com$1</a> results in broken redirects.</p>
<p>You&#8217;re missing a /</p>
<p>RedirectMatch 301 (.*) <a href="http://www.your-domain.com/$1" rel="nofollow">http://www.your-domain.com/$1</a> is what you want.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ashleigh</title>
		<link>http://www.happy-plastic.com/blogging/redirecting-old-wordpress-permalinks-to-a-new-domain/comment-page-1#comment-313</link>
		<dc:creator>Ashleigh</dc:creator>
		<pubDate>Mon, 11 May 2009 07:14:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.happy-plastic.com/?p=130#comment-313</guid>
		<description>Thanks Jenny.

^_^</description>
		<content:encoded><![CDATA[<p>Thanks Jenny.</p>
<p>^_^</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jenny Kumar</title>
		<link>http://www.happy-plastic.com/blogging/redirecting-old-wordpress-permalinks-to-a-new-domain/comment-page-1#comment-309</link>
		<dc:creator>Jenny Kumar</dc:creator>
		<pubDate>Sat, 09 May 2009 07:42:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.happy-plastic.com/?p=130#comment-309</guid>
		<description>I really liked your post.</description>
		<content:encoded><![CDATA[<p>I really liked your post.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
