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 Hiroaki.Kawai
Recipients Hiroaki.Kawai, neologix, pitrou
Date 2013-04-09.14:53:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CABD3daoic+F26=yv+_FF+PQ+_T-d_shvtO5gtHX5241w=WatYw@mail.gmail.com>
In-reply-to <1365518715.46.0.665562383233.issue17672@psf.upfronthosting.co.za>
Content
Client gets an exception in reading the socket, not in writing. Please run
the test code and see what happens.

2013/4/9 Charles-François Natali <report@bugs.python.org>

>
> Charles-François Natali added the comment:
>
> > sometimes RST was sent over the network instead of FIN
>
> Your client sends data, but the server never reads it: when a TCP socket
> is closed while there's still data in the input socket buffer, a RST is
> sent instead of a FIN. That's normal behaviour.
>
> ----------
> nosy: +neologix
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue17672>
> _______________________________________
>
History
Date User Action Args
2013-04-09 14:53:03Hiroaki.Kawaisetrecipients: + Hiroaki.Kawai, pitrou, neologix
2013-04-09 14:53:03Hiroaki.Kawailinkissue17672 messages
2013-04-09 14:53:02Hiroaki.Kawaicreate