Guy Kloss added the comment:
I know this issue is marked as fixed, and won't be backported to 2.6. But the
fix is simple enough to self perform on 2.6. Doing that I have discovered an
issue that might still be present with the fix, as it was not discussed here,
yet, but is still related.
Whenever one does the same thing, but uses an SSL connection (HTTPS), the
socket.error is raised from within ssl.py (line 174).
Even though the send() call in httplib does not misbehave now, when using an
SSL encrypted connection the ssl module still throws you in front of a bus.
--
nosy: +guy.kloss
___
Python tracker
<http://bugs.python.org/issue5542>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com