--001636e0a7b4b3768e04771ae0da
Content-Type: text/plain; charset=UTF-8

From the OPs description of the problem, and the code presented, yes, the
rescue will catch the exception, but that will stop the loop.

So, if you're trying to get /missing.html, /broken.html,
/the_url_I_want.svg, and missing raises a 404, then that will get caught by
the rescue outside of the loop, and you won't make further requests.  In
other words:

input:
http://site.com/missing.html
http://site.com/aweseom.html

output:
Page Not Found

When what I understood Kyle to want from the output is something like
Page Not Found
"It's spelled 'awesome'"

Judson

On Thu, Oct 29, 2009 at 3:33 PM, Marnen Laibow-Koser <marnen / marnen.org>wrote:

> Marnen Laibow-Koser wrote:
> > Judson Lester wrote:
> >> Your problem is that you're catching the exception outside of the loop.
> >
> > Should that matter?  The extension is still happening after the begin,
> > so the rescue should catch it.
>
> Sorry, I meant "exception", not "extension", obviously! :P
>
> [...]
> >
> > Best,
> > --
> > Marnen Laibow-Koser
> > http://www.marnen.org
> > marnen / marnen.org
>
> --
> Posted via http://www.ruby-forum.com/.
>
>

--001636e0a7b4b3768e04771ae0da--