<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: The anatomy of a server sided redirect: 301, 302 and 307 illuminated SEO wise</title>
	<link>http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/</link>
	<description>If you've read my articles somewhere on the Internet, expect something different here.</description>
	<pubDate>Thu, 02 Sep 2010 12:01:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>By: SEO Toxin: Directory-like URI Structures &#124; SEO Bullshit</title>
		<link>http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-2250</link>
		<dc:creator>SEO Toxin: Directory-like URI Structures &#124; SEO Bullshit</dc:creator>
		<pubDate>Tue, 02 Feb 2010 18:24:19 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-2250</guid>
		<description>[...] server name canonicalization), and search engines won&#8217;t index any product page, because five redirects in a row is the maximum. There&#8217;s no maximum when it comes to SEO myths, so probably most [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] server name canonicalization), and search engines won&#8217;t index any product page, because five redirects in a row is the maximum. There&#8217;s no maximum when it comes to SEO myths, so probably most [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: As if sloppy social media users ain&#8217;t bad enough &#8230; search engines support traffic theft</title>
		<link>http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-1868</link>
		<dc:creator>As if sloppy social media users ain&#8217;t bad enough &#8230; search engines support traffic theft</dc:creator>
		<pubDate>Mon, 26 Oct 2009 19:19:19 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-1868</guid>
		<description>[...] what a mess. The candidate from Redmond fails totally on understanding the HTTP protocol. Their search index is flooded with a bazillion of URI-only listings that all do a 301 redirect, [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] what a mess. The candidate from Redmond fails totally on understanding the HTTP protocol. Their search index is flooded with a bazillion of URI-only listings that all do a 301 redirect, [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jehzeel Laurente</title>
		<link>http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-1844</link>
		<dc:creator>Jehzeel Laurente</dc:creator>
		<pubDate>Wed, 14 Oct 2009 07:07:45 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-1844</guid>
		<description>I still can't understand what's the difference between 302 and 307 redirection. :(

[302-found-elsewhere indicates crap. 307-temp-redirect-don't-cache is a cool way to tell the user agent that a resource must get requested under this address but the content will be delivered by another URI at the moment, or from frequently changing URIs ....]</description>
		<content:encoded><![CDATA[<p>I still can&#8217;t understand what&#8217;s the difference between 302 and 307 redirection. <img src='http://sebastians-pamphlets.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
<p>[302-found-elsewhere indicates crap. 307-temp-redirect-don&#8217;t-cache is a cool way to tell the user agent that a resource must get requested under this address but the content will be delivered by another URI at the moment, or from frequently changing URIs &#8230;.]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-1789</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Mon, 21 Sep 2009 16:40:50 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-1789</guid>
		<description>Good meaty article. It cleared up some points for me, so thanks for that. BTW, I've been using 310's for a while. Apparently, these are even more permanent than 301's.

[&lt;a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3"&gt;Wow&lt;/a&gt;. There's no such thing as a "310" alias for 410-your-spammy-link-status-is-Gone.]</description>
		<content:encoded><![CDATA[<p>Good meaty article. It cleared up some points for me, so thanks for that. BTW, I&#8217;ve been using 310&#8217;s for a while. Apparently, these are even more permanent than 301&#8217;s.</p>
<p>[<a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3">Wow</a>. There&#8217;s no such thing as a &#8220;310&#8243; alias for 410-your-spammy-link-status-is-Gone.]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Przekierowania HTTP &#124; TeMPOraL's devBlog</title>
		<link>http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-1771</link>
		<dc:creator>Przekierowania HTTP &#124; TeMPOraL's devBlog</dc:creator>
		<pubDate>Tue, 08 Sep 2009 05:50:08 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-1771</guid>
		<description>[...] jedno z nich powinno być powszechnie znane programistom PHP. Wpis ten oparty jest o post "The anatomy of server sided redirect" na blogu Sebastian's Pamphlets, specyfikacji HTTP/1.1, której wydrukowany fragment trzymam obok [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] jedno z nich powinno być powszechnie znane programistom PHP. Wpis ten oparty jest o post &#8220;The anatomy of server sided redirect&#8221; na blogu Sebastian&#8217;s Pamphlets, specyfikacji HTTP/1.1, której wydrukowany fragment trzymam obok [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Debugging robots.txt with Google Webmaster Tools</title>
		<link>http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-1746</link>
		<dc:creator>Debugging robots.txt with Google Webmaster Tools</dc:creator>
		<pubDate>Tue, 18 Aug 2009 17:32:12 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-1746</guid>
		<description>[...] URIs, driving you nuts until you check each URI&#8217;s HTTP response code for redirects (HTTP response codes 301, 302 and 307, as well as undelayed meta [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] URIs, driving you nuts until you check each URI&#8217;s HTTP response code for redirects (HTTP response codes 301, 302 and 307, as well as undelayed meta [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Klaus Johannes Rusch</title>
		<link>http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-1723</link>
		<dc:creator>Klaus Johannes Rusch</dc:creator>
		<pubDate>Mon, 10 Aug 2009 18:20:01 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-1723</guid>
		<description>Thanks for the detailed and informative pamphlet.

With the introduction of the canonical meta tag and the "merging" of related pages into one entity, passing link weight may become easier: http://www.atmedia.net/KlausRusch/blog/2009/08/seo-advice-redirect-wisely.html</description>
		<content:encoded><![CDATA[<p>Thanks for the detailed and informative pamphlet.</p>
<p>With the introduction of the canonical meta tag and the &#8220;merging&#8221; of related pages into one entity, passing link weight may become easier: <a href="http://www.atmedia.net/KlausRusch/blog/2009/08/seo-advice-redirect-wisely.html">http://www.atmedia.net/KlausRusch/blog/2009/08/seo-advice-redirect-wisely.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Effect of Using Short links? - Thirty Day Challenge Forums</title>
		<link>http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-1722</link>
		<dc:creator>The Effect of Using Short links? - Thirty Day Challenge Forums</dc:creator>
		<pubDate>Mon, 10 Aug 2009 15:12:05 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-1722</guid>
		<description>[...] the long answer is REALLY long -  The anatomy of a server sided redirect: 301, 302 and 307  I did some work on a currently-successful commercial URL shortener. After months of benchmarked [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] the long answer is REALLY long -  The anatomy of a server sided redirect: 301, 302 and 307  I did some work on a currently-successful commercial URL shortener. After months of benchmarked [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Douglas</title>
		<link>http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-1531</link>
		<dc:creator>Adam Douglas</dc:creator>
		<pubDate>Tue, 03 Feb 2009 11:22:43 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-1531</guid>
		<description>This you for this great article!  I wish I would have read it sooner. However I am confused as to what to do in my situation.

When maintenance or some other important reason occurs I have three temporary options in my custom CMS. Should the below three options listed below (if enabled) use 307 Temporary Redirect, 302 Temporary Moved or just have exceptions in my PHP code to ignore the regular process of getting the client requested content. Instead it renders a message to the client with no change to the HTTP status code or URL.

- Web site access disabled.
- Web site authentications (logins) disable.
- Web site downloads disabled (Non-HTML content, ie. PDF, ZIPs, documents, etc.)

I look forward to your response on this matter. I want to do what is right and not just do it my way because it appears to work fine.</description>
		<content:encoded><![CDATA[<p>This you for this great article!  I wish I would have read it sooner. However I am confused as to what to do in my situation.</p>
<p>When maintenance or some other important reason occurs I have three temporary options in my custom CMS. Should the below three options listed below (if enabled) use 307 Temporary Redirect, 302 Temporary Moved or just have exceptions in my PHP code to ignore the regular process of getting the client requested content. Instead it renders a message to the client with no change to the HTTP status code or URL.</p>
<p>- Web site access disabled.<br />
- Web site authentications (logins) disable.<br />
- Web site downloads disabled (Non-HTML content, ie. PDF, ZIPs, documents, etc.)</p>
<p>I look forward to your response on this matter. I want to do what is right and not just do it my way because it appears to work fine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BlueBoden</title>
		<link>http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-1449</link>
		<dc:creator>BlueBoden</dc:creator>
		<pubDate>Thu, 16 Oct 2008 16:45:55 +0000</pubDate>
		<guid>http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-1449</guid>
		<description>Very nice post about http redirects. I'm sure a lot of beginners will find this useful.

Remember though, broken links to css files and images, can be easily solved by using root-relative paths instead of relative paths.</description>
		<content:encoded><![CDATA[<p>Very nice post about http redirects. I&#8217;m sure a lot of beginners will find this useful.</p>
<p>Remember though, broken links to css files and images, can be easily solved by using root-relative paths instead of relative paths.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
