Hi, I noticed a difference in how errors can be returned between a plain TCP connection and a TLS connection.
With plain TCP, a client write followed by a server read and finally a client read results in the client getting a "connection reset" error. This is expected and reflects the RST seen in a TCP packet as can be seen using tcpdump. Conversely, the same operations in a TLS connection does not result in a "connection reset" error, or any error at all, despite seeing the RST happening on the underlying TCP connection. Can anyone explain this difference in behaviour? Is it expected? I have written a test to show the difference: https://gist.github.com/mjgarton/3f583ac323ffecbfc478bb05724eb000 -- Martin. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
