homepage

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.

Author pitrou
Recipients Hiroaki.Kawai, neologix, pitrou
Date 2013年04月09日.15:13:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <485153595.38437081.1365520395027.JavaMail.root@zimbra10-e2.priv.proxad.net>
In-reply-to <CABD3dapXfrcWfN2QZ2o5N-NHBN5G0OzS+Jg24Up1z5xQ-RDhdA@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.
Please re-read your own code. The server does:
+ def handle(self):
+ self.wfile.write("123")
and the client does:
+ s.recv(3)
So, yes, the client is able to read the 3 bytes that the server sent.
It's only when you are trying to read an additional byte that an
exception is raised, because the TCP connection has been closed
by the server.
History
Date User Action Args
2013年04月09日 15:13:21pitrousetrecipients: + pitrou, neologix, Hiroaki.Kawai
2013年04月09日 15:13:21pitroulinkissue17672 messages
2013年04月09日 15:13:21pitroucreate

AltStyle によって変換されたページ (->オリジナル) /