Message186428
| Author |
Hiroaki.Kawai |
| Recipients |
Hiroaki.Kawai, neologix, pitrou |
| Date |
2013年04月09日.15:20:55 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CABD3daqokp2NUsc0nNik-LGg5YZWkU3EGJc1wDVzsYRZjhybxg@mail.gmail.com> |
| In-reply-to |
<1365519928.95.0.936605033412.issue17672@psf.upfronthosting.co.za> |
| Content |
The error looks like : SSLError(8, '_ssl.c:1363: EOF occurred in violation
of protocol')
But why we see "in violation of protocol" here?
2013年4月10日 Antoine Pitrou <report@bugs.python.org>
>
> Antoine Pitrou added the comment:
>
> > Client gets an exception in reading the socket, not in writing.
>
> Yes, it does, and the exception bears the error code SSL_ERROR_EOF (8),
> which is expected here.
>
> The question is: why would you expect reading *not* to raise an exception
> while the remote end of the connection has been closed? TCPStreamHandler
> will only keep the connection alive as long as the handle() method is
> running, the connection is disposed of afterwards.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue17672>
> _______________________________________
> |
|