Message186425
| Author |
Hiroaki.Kawai |
| Recipients |
Hiroaki.Kawai, neologix, pitrou |
| Date |
2013年04月09日.15:05:38 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CABD3dapXfrcWfN2QZ2o5N-NHBN5G0OzS+Jg24Up1z5xQ-RDhdA@mail.gmail.com> |
| In-reply-to |
<CAH_1eM3tKucou3AOkeT-hVfC1c1eiX5d3Zw94ApMMs9ywoz+RQ@mail.gmail.com> |
| Content |
As an interface of ssl socket, server does not have to read, just write
some data.
The client side should be able to read the bytes that ther server sent. The
problem is that client will sometimes raise an unexpected SSLError in
reading the ssl socket because server side does not shutdown the ssl
session cleanly.
2013年4月9日 Charles-François Natali <report@bugs.python.org>
>
> Charles-François Natali added the comment:
>
> > Client gets an exception in reading the socket, not in writing. Please
> run
> > the test code and see what happens.
>
> Of course it gets ECONNRESET on subsequent recv(), that's how TCP works.
>
> Just make your handler read from the socket and it won't happen anymore.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue17672>
> _______________________________________
> |
|