This is the way of TCP sockets. “Write” means to put the bytes into the kernel
send buffer and is essentially nonblocking within that buffer size. Connection
errors are more often detected on the next read operation, which naturally
blocks waiting for the next network event / packet.
//jb
On
Hi,
I am experiencing an issue in *Conn.Write() which is not detecting that the
connection was closed in the server.
Below you can find demo SSL server and client which hosted on same go
project.
The problem is that the following line doesn't detect closed
socket/connection:
