Message 186424 - Python tracker

➜

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.

In-reply-to
Author	pitrou
Recipients	Hiroaki.Kawai, neologix, pitrou
Date	2013年04月09日.15:05:28
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1365519928.95.0.936605033412.issue17672@psf.upfronthosting.co.za>

Content
> 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.

Content

> 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.

History
Date	User	Action	Args
2013年04月09日 15:05:28	pitrou	set	recipients: + pitrou, neologix, Hiroaki.Kawai
2013年04月09日 15:05:28	pitrou	set	messageid: <1365519928.95.0.936605033412.issue17672@psf.upfronthosting.co.za>
2013年04月09日 15:05:28	pitrou	link	issue17672 messages
2013年04月09日 15:05:28	pitrou	create

homepage