Message186426
| Author |
neologix |
| Recipients |
Hiroaki.Kawai, neologix, pitrou |
| Date |
2013年04月09日.15:10:21 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAH_1eM1eWxCf3fN+gGb5W35m=VEcdH91H-v_q2LW30wNhUMajQ@mail.gmail.com> |
| 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. The
> problem is that client will sometimes raise an unexpected SSLError in
> reading the ssl socket because server side does not shutdown the ssl
> session cleanly.
Once again, that's not how TCP works.
If your server doesn't read data that the client sent it, a RST will
be sent when the server closes its end.
Please do read the TCP spec, or use google:
http://cs.baylor.edu/~donahoo/practical/CSockets/TCPRST.pdf
I suggest closing this issue... |
|