<?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: An Informative 404 Page</title>
	<atom:link href="http://designshack.co.uk/articles/an-informative-404-page/feed" rel="self" type="application/rss+xml" />
	<link>http://designshack.co.uk/articles/an-informative-404-page</link>
	<description>Inspiration, CSS Gallery &#38; Community News</description>
	<lastBuildDate>Tue, 16 Mar 2010 23:16:29 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Stinky82</title>
		<link>http://designshack.co.uk/articles/an-informative-404-page#comment-1403</link>
		<dc:creator>Stinky82</dc:creator>
		<pubDate>Fri, 23 Oct 2009 01:22:28 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=171#comment-1403</guid>
		<description>As is the case with medications. ,</description>
		<content:encoded><![CDATA[<p>As is the case with medications. ,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: angel</title>
		<link>http://designshack.co.uk/articles/an-informative-404-page#comment-339</link>
		<dc:creator>angel</dc:creator>
		<pubDate>Tue, 28 Oct 2008 01:17:02 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=171#comment-339</guid>
		<description>I need more information</description>
		<content:encoded><![CDATA[<p>I need more information</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jordan Payne</title>
		<link>http://designshack.co.uk/articles/an-informative-404-page#comment-278</link>
		<dc:creator>Jordan Payne</dc:creator>
		<pubDate>Sat, 11 Oct 2008 01:27:24 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=171#comment-278</guid>
		<description>The mailing idea isn&#039;t such a good one. If some moron attempts to attack your site, they may find that vulnerability - flooding your email inbox.

Instead i would advise using PHP&#039;s error handling functions and write to an error file.</description>
		<content:encoded><![CDATA[<p>The mailing idea isn&#8217;t such a good one. If some moron attempts to attack your site, they may find that vulnerability &#8211; flooding your email inbox.</p>
<p>Instead i would advise using PHP&#8217;s error handling functions and write to an error file.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Kindness</title>
		<link>http://designshack.co.uk/articles/an-informative-404-page#comment-234</link>
		<dc:creator>David Kindness</dc:creator>
		<pubDate>Tue, 01 Jul 2008 12:44:59 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=171#comment-234</guid>
		<description>Yep for anything other than a simple site this method is just going to fill your inbox up, not to mention the possibility of being spammed to death.

As others suggested a combined approach of using your webstats and a log file would be more appropriate.

</description>
		<content:encoded><![CDATA[<p>Yep for anything other than a simple site this method is just going to fill your inbox up, not to mention the possibility of being spammed to death.</p>
<p>As others suggested a combined approach of using your webstats and a log file would be more appropriate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Lindén</title>
		<link>http://designshack.co.uk/articles/an-informative-404-page#comment-151</link>
		<dc:creator>Daniel Lindén</dc:creator>
		<pubDate>Mon, 23 Jun 2008 04:22:27 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=171#comment-151</guid>
		<description>Well, instead of emailing admin a database or log-file would be better. By using error-codes you can keep track of which messages that already has been submited and make it without spam. My first application was much like that, but later on I started to work with log-files which to me is the best solution, it even looks cool.</description>
		<content:encoded><![CDATA[<p>Well, instead of emailing admin a database or log-file would be better. By using error-codes you can keep track of which messages that already has been submited and make it without spam. My first application was much like that, but later on I started to work with log-files which to me is the best solution, it even looks cool.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will</title>
		<link>http://designshack.co.uk/articles/an-informative-404-page#comment-134</link>
		<dc:creator>Will</dc:creator>
		<pubDate>Fri, 06 Jun 2008 08:58:34 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=171#comment-134</guid>
		<description>I have them transferred to my inbox but i set a rule in outlook to automatically move them into my errors folder and i then sift through that folder weekly. Much better than receiving direct to inbox.</description>
		<content:encoded><![CDATA[<p>I have them transferred to my inbox but i set a rule in outlook to automatically move them into my errors folder and i then sift through that folder weekly. Much better than receiving direct to inbox.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Appleyard</title>
		<link>http://designshack.co.uk/articles/an-informative-404-page#comment-133</link>
		<dc:creator>David Appleyard</dc:creator>
		<pubDate>Fri, 06 Jun 2008 08:20:58 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=171#comment-133</guid>
		<description>You have all raised some very good points. This is mainly useful as a (very) temporary measure. When you launch a new site design or restructure it, it does allow you to find out the very common problematic pages easily. Another solution could be to write each 404 error to a database, then show a summary of the most popular errors.</description>
		<content:encoded><![CDATA[<p>You have all raised some very good points. This is mainly useful as a (very) temporary measure. When you launch a new site design or restructure it, it does allow you to find out the very common problematic pages easily. Another solution could be to write each 404 error to a database, then show a summary of the most popular errors.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik Reagan</title>
		<link>http://designshack.co.uk/articles/an-informative-404-page#comment-192</link>
		<dc:creator>Erik Reagan</dc:creator>
		<pubDate>Fri, 06 Jun 2008 06:19:14 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=171#comment-192</guid>
		<description>I also agree. On any higher traffic site this would bombard someone with emails if a user just typed junk in for some reason. If you REALLY want to go a custom route (and not use a statistics or analytics program readily available) I would suggest writing these results to a file instead. If you want to get &#039;fancy&#039; you can also create a cron job to mail the results weekly or however often you prefer.</description>
		<content:encoded><![CDATA[<p>I also agree. On any higher traffic site this would bombard someone with emails if a user just typed junk in for some reason. If you REALLY want to go a custom route (and not use a statistics or analytics program readily available) I would suggest writing these results to a file instead. If you want to get &#8216;fancy&#8217; you can also create a cron job to mail the results weekly or however often you prefer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh Harbaugh</title>
		<link>http://designshack.co.uk/articles/an-informative-404-page#comment-191</link>
		<dc:creator>Josh Harbaugh</dc:creator>
		<pubDate>Fri, 06 Jun 2008 06:13:25 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=171#comment-191</guid>
		<description>I agree. Unless you&#039;re dealing with a smaller site that wouldn&#039;t generate as many 404s I would be looking to site statistics or analytics for page display errors.</description>
		<content:encoded><![CDATA[<p>I agree. Unless you&#8217;re dealing with a smaller site that wouldn&#8217;t generate as many 404s I would be looking to site statistics or analytics for page display errors.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Virgil</title>
		<link>http://designshack.co.uk/articles/an-informative-404-page#comment-187</link>
		<dc:creator>Virgil</dc:creator>
		<pubDate>Thu, 05 Jun 2008 12:12:54 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=171#comment-187</guid>
		<description>I can see the usefullness of knowing what errors people are getting but that should be handled by your statistic program. My inbox is full enough with spam and like Martin suggests there is the possibility of people expoiting it and overflowing your email, like they do not already have enough people expoiting contact forms etc. or email bots etc.</description>
		<content:encoded><![CDATA[<p>I can see the usefullness of knowing what errors people are getting but that should be handled by your statistic program. My inbox is full enough with spam and like Martin suggests there is the possibility of people expoiting it and overflowing your email, like they do not already have enough people expoiting contact forms etc. or email bots etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://designshack.co.uk/articles/an-informative-404-page#comment-186</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Thu, 05 Jun 2008 11:01:25 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=171#comment-186</guid>
		<description>Ooh, 404. *reloads*. Ooh, again. *reloads*. Hey, perhaps I can annoy the admin! *reloads 10 times*. I can do that better. *uses a script to call the page 2000 times*.

Not to mention the potential XSS issues. If you do a tutorial, please make sure the outcome is complete.</description>
		<content:encoded><![CDATA[<p>Ooh, 404. *reloads*. Ooh, again. *reloads*. Hey, perhaps I can annoy the admin! *reloads 10 times*. I can do that better. *uses a script to call the page 2000 times*.</p>
<p>Not to mention the potential XSS issues. If you do a tutorial, please make sure the outcome is complete.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amy</title>
		<link>http://designshack.co.uk/articles/an-informative-404-page#comment-182</link>
		<dc:creator>Amy</dc:creator>
		<pubDate>Wed, 04 Jun 2008 13:00:59 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=171#comment-182</guid>
		<description>I use Drupal and I have a neat module installed called &quot;search404&quot;. When a user enters a URL that does not exist, the site actually performs a search on the last bit of the URL and brings you to a page of results.
</description>
		<content:encoded><![CDATA[<p>I use Drupal and I have a neat module installed called &#8220;search404&#8243;. When a user enters a URL that does not exist, the site actually performs a search on the last bit of the URL and brings you to a page of results.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
