<?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: How To Customise Your 404 Page</title>
	<atom:link href="http://www.sitepoint.com/blogs/2009/05/13/how-to-customise-your-404-page/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2009/05/13/how-to-customise-your-404-page/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<lastBuildDate>Mon, 23 Nov 2009 01:39:24 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: tintedPixel</title>
		<link>http://www.sitepoint.com/blogs/2009/05/13/how-to-customise-your-404-page/comment-page-1/#comment-925848</link>
		<dc:creator>tintedPixel</dc:creator>
		<pubDate>Thu, 21 May 2009 21:07:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=9409#comment-925848</guid>
		<description>@marty Indeed, webmasters should be using (best practices) that include proper redirects in .htaccess when pages are moved or become obsolete - though I don&#039;t think its lazy. But creating a 404 that provides options that let the user get back on track seems like a good idea as well, don&#039;t you think?

@yogomozilla Bingo! If the error pages don&#039;t provide the correct response headers, the error becomes just another page. Basically defeating the purpose.


My 2 pennies.</description>
		<content:encoded><![CDATA[<p>@marty Indeed, webmasters should be using (best practices) that include proper redirects in .htaccess when pages are moved or become obsolete &#8211; though I don&#8217;t think its lazy. But creating a 404 that provides options that let the user get back on track seems like a good idea as well, don&#8217;t you think?</p>
<p>@yogomozilla Bingo! If the error pages don&#8217;t provide the correct response headers, the error becomes just another page. Basically defeating the purpose.</p>
<p>My 2 pennies.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: CurlyB</title>
		<link>http://www.sitepoint.com/blogs/2009/05/13/how-to-customise-your-404-page/comment-page-1/#comment-925812</link>
		<dc:creator>CurlyB</dc:creator>
		<pubDate>Wed, 20 May 2009 21:17:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=9409#comment-925812</guid>
		<description>I fail to see how the attack on Microsoft by Skweekah &lt;blockquote&gt;Skweekah Says: “Oh no, it appears that youre using a Windows-based operating system…”
&lt;/blockquote&gt;
Will impres a user ending up with a 404 error because YOU have a problem on your website.
Blaming others is no answer.</description>
		<content:encoded><![CDATA[<p>I fail to see how the attack on Microsoft by Skweekah<br />
<blockquote>Skweekah Says: “Oh no, it appears that youre using a Windows-based operating system…”
</blockquote></p>
<p>Will impres a user ending up with a 404 error because YOU have a problem on your website.<br />
Blaming others is no answer.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: dianemcken</title>
		<link>http://www.sitepoint.com/blogs/2009/05/13/how-to-customise-your-404-page/comment-page-1/#comment-925640</link>
		<dc:creator>dianemcken</dc:creator>
		<pubDate>Fri, 15 May 2009 15:46:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=9409#comment-925640</guid>
		<description>I don&#039;t like web sites that blame it on me that their page is not found.  Saying &quot;you seem a bit lost&quot; to a potential customer doesn&#039;t come across very well.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t like web sites that blame it on me that their page is not found.  Saying &#8220;you seem a bit lost&#8221; to a potential customer doesn&#8217;t come across very well.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Stevie D</title>
		<link>http://www.sitepoint.com/blogs/2009/05/13/how-to-customise-your-404-page/comment-page-1/#comment-925630</link>
		<dc:creator>Stevie D</dc:creator>
		<pubDate>Fri, 15 May 2009 12:38:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=9409#comment-925630</guid>
		<description>&lt;blockquote&gt;Out of interest, when you accidentally land on a 404 Error page, do you hit the back button without thinking any more about it? Or do you try some of the suggested links?&lt;/blockquote&gt;
It depends how strong the information scent is. If I think the content will be on the site &lt;em&gt;and&lt;/em&gt; I think the site architecture is sufficient that I will be able to find the correct page, I&#039;ll persist. More often, I&#039;ll go back to Google and do a site-restricted search, or just give up. That&#039;s particularly true if it&#039;s a generic 404 page that shows little interest in being helpful. Because let&#039;s be honest, we all know that &quot;cool URLs don&#039;t change&quot;, and if they haven&#039;t bothered to map the old URL onto the new one, the chances are that they aren&#039;t taking all that much care with the rest of the site either.</description>
		<content:encoded><![CDATA[<blockquote><p>Out of interest, when you accidentally land on a 404 Error page, do you hit the back button without thinking any more about it? Or do you try some of the suggested links?</p></blockquote>
<p>It depends how strong the information scent is. If I think the content will be on the site <em>and</em> I think the site architecture is sufficient that I will be able to find the correct page, I&#8217;ll persist. More often, I&#8217;ll go back to Google and do a site-restricted search, or just give up. That&#8217;s particularly true if it&#8217;s a generic 404 page that shows little interest in being helpful. Because let&#8217;s be honest, we all know that &#8220;cool URLs don&#8217;t change&#8221;, and if they haven&#8217;t bothered to map the old URL onto the new one, the chances are that they aren&#8217;t taking all that much care with the rest of the site either.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: marty</title>
		<link>http://www.sitepoint.com/blogs/2009/05/13/how-to-customise-your-404-page/comment-page-1/#comment-925571</link>
		<dc:creator>marty</dc:creator>
		<pubDate>Thu, 14 May 2009 08:44:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=9409#comment-925571</guid>
		<description>or be lazy and use .htaccess</description>
		<content:encoded><![CDATA[<p>or be lazy and use .htaccess</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Skweekah</title>
		<link>http://www.sitepoint.com/blogs/2009/05/13/how-to-customise-your-404-page/comment-page-1/#comment-925569</link>
		<dc:creator>Skweekah</dc:creator>
		<pubDate>Thu, 14 May 2009 05:00:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=9409#comment-925569</guid>
		<description>Im going to be a stick in the mud here and say I dont like corny 404 pages. It&#039;s just my opinion. But I still find this article of value and who knows, I may yet create my own corny 404 error page, like &quot;Oh no, it appears that youre using a Windows-based operating system...&quot;</description>
		<content:encoded><![CDATA[<p>Im going to be a stick in the mud here and say I dont like corny 404 pages. It&#8217;s just my opinion. But I still find this article of value and who knows, I may yet create my own corny 404 error page, like &#8220;Oh no, it appears that youre using a Windows-based operating system&#8230;&#8221;</p>]]></content:encoded>
	</item>
	<item>
		<title>By: yogomozilla</title>
		<link>http://www.sitepoint.com/blogs/2009/05/13/how-to-customise-your-404-page/comment-page-1/#comment-925566</link>
		<dc:creator>yogomozilla</dc:creator>
		<pubDate>Thu, 14 May 2009 02:59:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=9409#comment-925566</guid>
		<description>&quot;A 404 page is a HTTP standard response code&quot;
- the page isn&#039;t the response code - &quot;404&quot; is the HTTP response code returned in the HTTP response headers from the remote server (http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.5).
The page is just some content (possibly HTML) that happens to be served with a 404 response.

If you are syndicating content from other sites or working with web services getting a 404 response code in an HTTP request means that the content is no longer there. This can trigger error logging on your side so you can determine what has happened and take measures to get things working again.

The cardinal sin is to serve a &quot;content not found page&quot; with a 200 OK response. Yeah, it might say &quot;content not found&quot; in the response document but to a web service that 200 OK response means &quot;yes the content is there&quot; - even if the HTML in the response contains text suggesting that the content is not found.

The 404 response also tells Google and other search engines that the page no longer exists, meaning they should be removed from the search index.

Out of the examples you&#039;ve given, the DigiGuru and Blue Daniel sites get it wrong by serving the 404 page as &quot;200 OK&quot; !fail!

; yogo</description>
		<content:encoded><![CDATA[<p>&#8220;A 404 page is a HTTP standard response code&#8221;<br />
- the page isn&#8217;t the response code &#8211; &#8220;404&#8243; is the HTTP response code returned in the HTTP response headers from the remote server (<a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.5)" rel="nofollow">http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.5)</a>.<br />
The page is just some content (possibly HTML) that happens to be served with a 404 response.</p>
<p>If you are syndicating content from other sites or working with web services getting a 404 response code in an HTTP request means that the content is no longer there. This can trigger error logging on your side so you can determine what has happened and take measures to get things working again.</p>
<p>The cardinal sin is to serve a &#8220;content not found page&#8221; with a 200 OK response. Yeah, it might say &#8220;content not found&#8221; in the response document but to a web service that 200 OK response means &#8220;yes the content is there&#8221; &#8211; even if the HTML in the response contains text suggesting that the content is not found.</p>
<p>The 404 response also tells Google and other search engines that the page no longer exists, meaning they should be removed from the search index.</p>
<p>Out of the examples you&#8217;ve given, the DigiGuru and Blue Daniel sites get it wrong by serving the 404 page as &#8220;200 OK&#8221; !fail!</p>
<p>; yogo</p>]]></content:encoded>
	</item>
	<item>
		<title>By: cranial-bore</title>
		<link>http://www.sitepoint.com/blogs/2009/05/13/how-to-customise-your-404-page/comment-page-1/#comment-925561</link>
		<dc:creator>cranial-bore</dc:creator>
		<pubDate>Wed, 13 May 2009 23:44:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=9409#comment-925561</guid>
		<description>The risk with designing a great 404 page is that it might never be seen.</description>
		<content:encoded><![CDATA[<p>The risk with designing a great 404 page is that it might never be seen.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: George Susini</title>
		<link>http://www.sitepoint.com/blogs/2009/05/13/how-to-customise-your-404-page/comment-page-1/#comment-925554</link>
		<dc:creator>George Susini</dc:creator>
		<pubDate>Wed, 13 May 2009 19:55:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=9409#comment-925554</guid>
		<description>Very creative, Those are great ! I am not sure I would put sponsors on the page like CSS Scoop though, that would surely drive customers away thinking they hit a link site.</description>
		<content:encoded><![CDATA[<p>Very creative, Those are great ! I am not sure I would put sponsors on the page like CSS Scoop though, that would surely drive customers away thinking they hit a link site.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: My220x</title>
		<link>http://www.sitepoint.com/blogs/2009/05/13/how-to-customise-your-404-page/comment-page-1/#comment-925553</link>
		<dc:creator>My220x</dc:creator>
		<pubDate>Wed, 13 May 2009 19:43:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=9409#comment-925553</guid>
		<description>Great 404 error pages there, it&#039;s nice to see something better then the default 404 ugly error page.</description>
		<content:encoded><![CDATA[<p>Great 404 error pages there, it&#8217;s nice to see something better then the default 404 ugly error page.</p>]]></content:encoded>
	</item>
</channel>
</rss>
