More socket strangeness

Today's fun fact:

If you're on Windows XP, and you have a TCP socket, and you have set SO_SNDBUF to 0 in order to do your own sender buffering, and you have called WSASend to start an overlapped send operation and Windows has called your callback stating the the send succeeded, and the other end of the socket is on the same machine, and that other end has not yet read the data you wrote, and you then call shutdown() to close the sending end of the socket, then the connection will be reset!

It works fine if you never touch SO_SNDBUF at all. But it doesn't help to set SO_SNDBUF to a nonzero value only just before shutdown()...


  1. Very interesting info !Perfect just what I was looking for!
    Here is my web page


  2. Thanks for sharing the information keep updating, looking forward to more post.
    Nice post ! I love its your site after reading ! thanks for sharing. I would like to use the ability of saying thanks to you for that professional guidance I have usually enjoyed checking out your site.
    Divorce Lawyers LoudounVA
    Divorce Lawyers Great Falls VA

  3. It's quite sweet and profound. This is an extremely cool blog. keep sharing. international recruitment process