<?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: Putting HTTP status codes to use with Rails</title>
	<atom:link href="http://techblog.floorplanner.com/2008/03/11/putting-http-status-codes-to-use-with-rails/feed/" rel="self" type="application/rss+xml" />
	<link>http://techblog.floorplanner.com/2008/03/11/putting-http-status-codes-to-use-with-rails/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Fri, 20 Nov 2009 23:38:19 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: skelkingur</title>
		<link>http://techblog.floorplanner.com/2008/03/11/putting-http-status-codes-to-use-with-rails/comment-page-1/#comment-593</link>
		<dc:creator>skelkingur</dc:creator>
		<pubDate>Tue, 05 May 2009 17:08:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.suite75.net/blog/dev/putting-http-status-codes-to-use-with-rails.html#comment-593</guid>
		<description>Very nice! Helped us a lot in a small browser game we&#039;re currently developing. We had some serious trouble with those HTTP 500 errors. Thankfully they are now gone :)

Keep posting!
skel</description>
		<content:encoded><![CDATA[<p>Very nice! Helped us a lot in a small browser game we&#8217;re currently developing. We had some serious trouble with those HTTP 500 errors. Thankfully they are now gone <img src='http://techblog.floorplanner.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Keep posting!<br />
skel</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Willem van Bergen</title>
		<link>http://techblog.floorplanner.com/2008/03/11/putting-http-status-codes-to-use-with-rails/comment-page-1/#comment-355</link>
		<dc:creator>Willem van Bergen</dc:creator>
		<pubDate>Thu, 29 Jan 2009 13:21:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.suite75.net/blog/dev/putting-http-status-codes-to-use-with-rails.html#comment-355</guid>
		<description>You&#039;re right. After looking into it, I found that rescue without a class will only catch StandardErrors, and no Exceptions. I thought it was the other way around. 

This has nothing to do with Rails though: it&#039;s a Ruby issue. The code example works just fine, because I use rescue_from with a specific class. However, deriving from StandardError is better, so I will adjust the sample code and the http_status_exceptions plugin.</description>
		<content:encoded><![CDATA[<p>You&#8217;re right. After looking into it, I found that rescue without a class will only catch StandardErrors, and no Exceptions. I thought it was the other way around. </p>
<p>This has nothing to do with Rails though: it&#8217;s a Ruby issue. The code example works just fine, because I use rescue_from with a specific class. However, deriving from StandardError is better, so I will adjust the sample code and the http_status_exceptions plugin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jan-Willem</title>
		<link>http://techblog.floorplanner.com/2008/03/11/putting-http-status-codes-to-use-with-rails/comment-page-1/#comment-354</link>
		<dc:creator>Jan-Willem</dc:creator>
		<pubDate>Thu, 29 Jan 2009 11:56:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.suite75.net/blog/dev/putting-http-status-codes-to-use-with-rails.html#comment-354</guid>
		<description>There is a little &quot;mistake&quot; in your examplecode. All your rails errors should be raised from StandardError instead of Exception. Also you should rescue StandardError instead of Exception.

StandardError is the base error class from rails. Which derives from Exception. Exception is ment for exceptions occurring outside the Rails framework.</description>
		<content:encoded><![CDATA[<p>There is a little &#8220;mistake&#8221; in your examplecode. All your rails errors should be raised from StandardError instead of Exception. Also you should rescue StandardError instead of Exception.</p>
<p>StandardError is the base error class from rails. Which derives from Exception. Exception is ment for exceptions occurring outside the Rails framework.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Willem van Bergen</title>
		<link>http://techblog.floorplanner.com/2008/03/11/putting-http-status-codes-to-use-with-rails/comment-page-1/#comment-185</link>
		<dc:creator>Willem van Bergen</dc:creator>
		<pubDate>Mon, 24 Nov 2008 11:13:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.suite75.net/blog/dev/putting-http-status-codes-to-use-with-rails.html#comment-185</guid>
		<description>That&#039;s weird. For some reason, looking for these static files in the public directory seems to be bypassed. I assume this occurs in development mode. Can you copy and paste the log output when you request such a file? Do you have a generic route that catches all URLs by any chance?

If you can resolve this issue, I would appreciate it if you can tell me what was causing it.</description>
		<content:encoded><![CDATA[<p>That&#8217;s weird. For some reason, looking for these static files in the public directory seems to be bypassed. I assume this occurs in development mode. Can you copy and paste the log output when you request such a file? Do you have a generic route that catches all URLs by any chance?</p>
<p>If you can resolve this issue, I would appreciate it if you can tell me what was causing it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cyrile</title>
		<link>http://techblog.floorplanner.com/2008/03/11/putting-http-status-codes-to-use-with-rails/comment-page-1/#comment-183</link>
		<dc:creator>Cyrile</dc:creator>
		<pubDate>Mon, 24 Nov 2008 08:45:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.suite75.net/blog/dev/putting-http-status-codes-to-use-with-rails.html#comment-183</guid>
		<description>Hi there,

thanks for writing this piece of code. However, I wanted to warn you that, after adding in my environment.rb:

config.gem &#039;wvanbergen-http_status_exceptions&#039;, :lib =&gt; &#039;http_status_exceptions&#039;, :source =&gt; &#039;http://gems.github.com&#039;

and restart my server, I began to receive 404 errors on my JS, CSS and image files...

I am not quite sure what the problem is (I am still looking). I&#039;ll let you know if I find the cause of the problem.

I use Rails 2.1.1 and Ruby ruby 1.8.6 (2008-08-08 patchlevel 286) [i686-darwin8.11.1] (Entreprise Edition)</description>
		<content:encoded><![CDATA[<p>Hi there,</p>
<p>thanks for writing this piece of code. However, I wanted to warn you that, after adding in my environment.rb:</p>
<p>config.gem &#8216;wvanbergen-http_status_exceptions&#8217;, :lib =&gt; &#8216;http_status_exceptions&#8217;, :source =&gt; &#8216;http://gems.github.com&#8217;</p>
<p>and restart my server, I began to receive 404 errors on my JS, CSS and image files&#8230;</p>
<p>I am not quite sure what the problem is (I am still looking). I&#8217;ll let you know if I find the cause of the problem.</p>
<p>I use Rails 2.1.1 and Ruby ruby 1.8.6 (2008-08-08 patchlevel 286) [i686-darwin8.11.1] (Entreprise Edition)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fractious</title>
		<link>http://techblog.floorplanner.com/2008/03/11/putting-http-status-codes-to-use-with-rails/comment-page-1/#comment-145</link>
		<dc:creator>fractious</dc:creator>
		<pubDate>Fri, 07 Nov 2008 16:39:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.suite75.net/blog/dev/putting-http-status-codes-to-use-with-rails.html#comment-145</guid>
		<description>Nice one Willem, will check it out, cheers.</description>
		<content:encoded><![CDATA[<p>Nice one Willem, will check it out, cheers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Willem van Bergen</title>
		<link>http://techblog.floorplanner.com/2008/03/11/putting-http-status-codes-to-use-with-rails/comment-page-1/#comment-144</link>
		<dc:creator>Willem van Bergen</dc:creator>
		<pubDate>Sat, 01 Nov 2008 07:43:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.suite75.net/blog/dev/putting-http-status-codes-to-use-with-rails.html#comment-144</guid>
		<description>Hey fractious,
Some time after after I wrote this piece, I found the list of HTTP statuses in Rails as well. I have written a Rails plugin that creates exception classes for all these statuses, and handles these exceptions like they are handled in this post. Check it out if you&#039;re interested: http://github.com/wvanbergen/http_status_exceptions/tree/master</description>
		<content:encoded><![CDATA[<p>Hey fractious,<br />
Some time after after I wrote this piece, I found the list of HTTP statuses in Rails as well. I have written a Rails plugin that creates exception classes for all these statuses, and handles these exceptions like they are handled in this post. Check it out if you&#8217;re interested: <a href="http://github.com/wvanbergen/http_status_exceptions/tree/master" rel="nofollow">http://github.com/wvanbergen/http_status_exceptions/tree/master</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fractious</title>
		<link>http://techblog.floorplanner.com/2008/03/11/putting-http-status-codes-to-use-with-rails/comment-page-1/#comment-143</link>
		<dc:creator>fractious</dc:creator>
		<pubDate>Fri, 31 Oct 2008 11:59:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.suite75.net/blog/dev/putting-http-status-codes-to-use-with-rails.html#comment-143</guid>
		<description>Good post, just what I was looking for thanks.

Here&#039;s another that I found that lists all the codes that rails knows about along with their symbol representations. It also lists what status codes certain uncaught exceptions will generate.

http://blog.restphone.com/2007/12/17/rails-and-http-status-codes</description>
		<content:encoded><![CDATA[<p>Good post, just what I was looking for thanks.</p>
<p>Here&#8217;s another that I found that lists all the codes that rails knows about along with their symbol representations. It also lists what status codes certain uncaught exceptions will generate.</p>
<p><a href="http://blog.restphone.com/2007/12/17/rails-and-http-status-codes" rel="nofollow">http://blog.restphone.com/2007/12/17/rails-and-http-status-codes</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HTTP status exception handling plugin &#124; Floorplanner Tech Blog</title>
		<link>http://techblog.floorplanner.com/2008/03/11/putting-http-status-codes-to-use-with-rails/comment-page-1/#comment-122</link>
		<dc:creator>HTTP status exception handling plugin &#124; Floorplanner Tech Blog</dc:creator>
		<pubDate>Sun, 21 Sep 2008 11:01:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.suite75.net/blog/dev/putting-http-status-codes-to-use-with-rails.html#comment-122</guid>
		<description>[...] time ago, I wrote about putting HTTP status code to use for your Rails application. For my reinvigorated project, I wanted to apply the same technique. [...]</description>
		<content:encoded><![CDATA[<p>[...] time ago, I wrote about putting HTTP status code to use for your Rails application. For my reinvigorated project, I wanted to apply the same technique. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
