Comments on: OpenURI, Exceptions and HTTP Status Codes http://somethingsimilar.com/2007/08/07/openuri-exceptions-and-http-status-codes/ Just like it. Mon, 05 Jul 2010 01:42:43 +0000 http://wordpress.org/?v=2.8.4 hourly 1 By: Anders E http://somethingsimilar.com/2007/08/07/openuri-exceptions-and-http-status-codes/comment-page-1/#comment-12956 Anders E Wed, 24 Jun 2009 11:47:28 +0000 http://www.somethingsimilar.com/wordpress/2007/08/07/openuri-exceptions-and-http-status-codes/#comment-12956 <p>Re: Jesse Newland</p> <p>You can set :redirect=>false like: uri.read(:redirect=>false)</p> <p>This is kinda needed to be able to handle 301 properly, since you are supposed to update your references whenever you find a permanent redirect like that. At least, this is the only decent way of achieving this that I've come across.</p> <p>Thanks for your post Jeff!</p> Re: Jesse Newland

You can set :redirect=>false like: uri.read(:redirect=>false)

This is kinda needed to be able to handle 301 properly, since you are supposed to update your references whenever you find a permanent redirect like that. At least, this is the only decent way of achieving this that I’ve come across.

Thanks for your post Jeff!

]]> By: Jesse Newland http://somethingsimilar.com/2007/08/07/openuri-exceptions-and-http-status-codes/comment-page-1/#comment-992 Jesse Newland Wed, 15 Aug 2007 20:27:26 +0000 http://www.somethingsimilar.com/wordpress/2007/08/07/openuri-exceptions-and-http-status-codes/#comment-992 <p>Actually, this isn't exactly correct - open-uri and rest-open-uri swallow 301, 302, 303, and 307 status codes, follow the redirection w/o exception, and tell you they received a 200.</p> <p>This is causing some breakage in rfeedparser, as I've detailed here:</p> <p>http://rubyforge.org/tracker/index.php?func=detail&aid=13073&group_id=3309&atid=12738</p> Actually, this isn’t exactly correct – open-uri and rest-open-uri swallow 301, 302, 303, and 307 status codes, follow the redirection w/o exception, and tell you they received a 200.

This is causing some breakage in rfeedparser, as I’ve detailed here:

http://rubyforge.org/tracker/index.php?func=detail&aid=13073&group_id=3309&atid=12738

]]>