This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients mrDoctorWho0.., r.david.murray
Date 2013-09-20.12:55:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1379681752.82.0.219890829428.issue19057@psf.upfronthosting.co.za>
In-reply-to
Content
I would guess that if you did a network trace you'd find out there really was a packet that did not arrive (a timeout).  Note that detecting this is complicated by the fact that ssl is involved.  (I don't know the details, but I remember someone saying that more than one packet may be involved in something that looks like a single event at the OpenSSL level.)

It is certainly *possible* that there is a bug at the OpenSSL or (less likely) the _ssl module level, but the first step in debugging it would be to get that network trace, I think...

As I said, though, I'm not an expert in this area, perhaps someone who is will have other suggestions.
History
Date User Action Args
2013-09-20 12:55:52r.david.murraysetrecipients: + r.david.murray, mrDoctorWho0..
2013-09-20 12:55:52r.david.murraysetmessageid: <1379681752.82.0.219890829428.issue19057@psf.upfronthosting.co.za>
2013-09-20 12:55:52r.david.murraylinkissue19057 messages
2013-09-20 12:55:52r.david.murraycreate