--0qt3EE9wi45a2ZFX
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Chris Morris (chrismo / clabs.org) wrote:

>   A connection attempt failed because the connected party
>   did not properly respond after a period of time, or
>   established connection failed because connected host
>   has failed to respond. - "connect(2)"
> 
> ... I understand a read timeout of 60, but why aren't all my errors like
> that? What causes the second error to occur, because it essentially says it
> was a timeout, right?

A read timeout is on an already established connection, this error seems
to come from the socket not being established at all.

It should be an exception like Errno::ETIMEDOUT (if you used #get)

-- 
Eric Hodel - drbrain / segment7.net - http://segment7.net
All messages signed with fingerprint:
FEC2 57F1 D465 EB15 5D6E  7C11 332A 551C 796C 9F04


--0qt3EE9wi45a2ZFX
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE+UUH3MypVHHlsnwQRAiLBAKD0/6Wwx6lQVIdm5h2RLD9q94l0VwCfefFk
ytl2IdhVHBdnhsTYj2iu7EoxW
-----END PGP SIGNATURE-----

--0qt3EE9wi45a2ZFX--