Comments on: not_found and error handlers for custom 404 and 500 responses http://www.gittr.com/index.php/archive/not_found-and-error-handlers-for-custom-404-and-500-responses/ eval("eval(\"eval(\\\"puts 'a ruby weblog'\\\")\")") Mon, 30 Jan 2012 23:01:38 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Ryan Tomayko http://www.gittr.com/index.php/archive/not_found-and-error-handlers-for-custom-404-and-500-responses/comment-page-1/#comment-70 Ryan Tomayko Wed, 10 Sep 2008 20:46:38 +0000 http://www.gittr.com/?p=52#comment-70 We should really make it easier to get at `request.env['sinatra.error']`. Maybe EventContent#error or EventContext#exception or something. We should really make it easier to get at `request.env[‘sinatra.error’]`. Maybe EventContent#error or EventContext#exception or something.

]]> By: sr http://www.gittr.com/index.php/archive/not_found-and-error-handlers-for-custom-404-and-500-responses/comment-page-1/#comment-69 sr Wed, 10 Sep 2008 20:25:43 +0000 http://www.gittr.com/?p=52#comment-69 note that #not_found is actually only a shorthand for error NotFound do 'err!' end note that #not_found is actually only a shorthand for

error NotFound do
‘err!’
 end

]]>