Hiroaki Kawai added the comment: 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 <rep...@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 <rep...@bugs.python.org> > <http://bugs.python.org/issue17672> > _______________________________________ > ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17672> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
