<?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: Basic Guide to .htaccess</title>
	<atom:link href="http://blog.westhost.com/2008/09/26/basic-guide-to-htaccess/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.westhost.com/blog/2008/09/26/basic-guide-to-htaccess/</link>
	<description>News, Announcements &#38; More</description>
	<lastBuildDate>Tue, 01 Nov 2011 13:20:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Tom</title>
		<link>http://www.westhost.com/blog/2008/09/26/basic-guide-to-htaccess/comment-page-1/#comment-2087</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Fri, 14 Nov 2008 16:02:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.westhost.com/?p=69#comment-2087</guid>
		<description>Beginners should also watch out for the difference between permanent and temporary redirects.


* Permanent redirects look something like this:

Redirect 301 /oldlocation.html http://www.foo.com/newlocation.html

- permanent redirects tell Google &amp; friends that a page has moved for good and they needn&#039;t check back to the original URL.
- this means any Google PageRank and search engine position will be transferred from the old page to the new location.
- this is hugely important, as it lets you change your site structure (&amp; even your domain name) without losing your search engine positions.


* Temporary redirects look something like this:

Redirect 302 /oldlocation.html http://www.foo.com/newlocation.html

- this tells Google &amp; friends that your change is only temporary and that they should always check back to the original URL.
- browsers automatically follow these redirections, but Google won&#039;t update it&#039;s listings.</description>
		<content:encoded><![CDATA[<p>Beginners should also watch out for the difference between permanent and temporary redirects.</p>
<p>* Permanent redirects look something like this:</p>
<p>Redirect 301 /oldlocation.html <a href="http://www.foo.com/newlocation.html" rel="nofollow">http://www.foo.com/newlocation.html</a></p>
<p>- permanent redirects tell Google &amp; friends that a page has moved for good and they needn&#8217;t check back to the original URL.<br />
- this means any Google PageRank and search engine position will be transferred from the old page to the new location.<br />
- this is hugely important, as it lets you change your site structure (&amp; even your domain name) without losing your search engine positions.</p>
<p>* Temporary redirects look something like this:</p>
<p>Redirect 302 /oldlocation.html <a href="http://www.foo.com/newlocation.html" rel="nofollow">http://www.foo.com/newlocation.html</a></p>
<p>- this tells Google &amp; friends that your change is only temporary and that they should always check back to the original URL.<br />
- browsers automatically follow these redirections, but Google won&#8217;t update it&#8217;s listings.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jefferson</title>
		<link>http://www.westhost.com/blog/2008/09/26/basic-guide-to-htaccess/comment-page-1/#comment-1720</link>
		<dc:creator>Jefferson</dc:creator>
		<pubDate>Wed, 22 Oct 2008 05:07:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.westhost.com/?p=69#comment-1720</guid>
		<description>The Apache web site has a number of useful documents. Nevertheless, a lot of trial and error seems to be required. If even a basic command doesn&#039;t work, make sure you added an override to httpd.conf (search the forum for more information).

http://httpd.apache.org/docs/2.0/howto/htaccess.html
http://httpd.apache.org/docs/2.0/mod/mod_rewrite.html
http://httpd.apache.org/docs/2.0/misc/rewriteguide.html</description>
		<content:encoded><![CDATA[<p>The Apache web site has a number of useful documents. Nevertheless, a lot of trial and error seems to be required. If even a basic command doesn&#8217;t work, make sure you added an override to httpd.conf (search the forum for more information).</p>
<p><a href="http://httpd.apache.org/docs/2.0/howto/htaccess.html" rel="nofollow">http://httpd.apache.org/docs/2.0/howto/htaccess.html</a><br />
<a href="http://httpd.apache.org/docs/2.0/mod/mod_rewrite.html" rel="nofollow">http://httpd.apache.org/docs/2.0/mod/mod_rewrite.html</a><br />
<a href="http://httpd.apache.org/docs/2.0/misc/rewriteguide.html" rel="nofollow">http://httpd.apache.org/docs/2.0/misc/rewriteguide.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kentli</title>
		<link>http://www.westhost.com/blog/2008/09/26/basic-guide-to-htaccess/comment-page-1/#comment-1496</link>
		<dc:creator>Kentli</dc:creator>
		<pubDate>Sat, 27 Sep 2008 09:05:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.westhost.com/?p=69#comment-1496</guid>
		<description>The basics are fairly easy to understand. Its rewriting dynamic URLs that stumps me, what with all the $1 $2 variables and cascading conditions.

Do you know of any simple .htaccess resources with LOTS of examples that can be copied/ modified?</description>
		<content:encoded><![CDATA[<p>The basics are fairly easy to understand. Its rewriting dynamic URLs that stumps me, what with all the $1 $2 variables and cascading conditions.</p>
<p>Do you know of any simple .htaccess resources with LOTS of examples that can be copied/ modified?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

