Client initiated close always runs into `close_timeout`

[baxterjo]

Client initiated close always runs into `close_timeout`

[aaugustin]

This is the behavior mandated by RFC 6455:

The underlying TCP connection, in most normal cases, SHOULD be closed
first by the server, so that it holds the TIME_WAIT state and not the
client (as this would prevent it from re-opening the connection for 2
maximum segment lifetimes (2MSL), while there is no corresponding
server impact as a TIME_WAIT connection is immediately reopened upon
a new SYN with a higher seq number). In abnormal cases (such as not
having received a TCP Close from the server after a reasonable amount
of time) a client MAY initiate the TCP Close. As such, when a server
is instructed to Close the WebSocket Connection it SHOULD initiate
a TCP Close immediately, and when a client is instructed to do the
same, it SHOULD wait for a TCP Close from the server.

If your server doesn't close the TCP connection immediately, then that's a bug in your server.

[aaugustin]

Of course, if the server is websockets, then that's a bug in websockets. I don't think that's the case because your issue refers only to the client side and because the TCP connection close behaviors are tested quite extensively in websockets' test suite.

[baxterjo]

Of course, if the server is websockets, then that's a bug in websockets. I don't think that's the case because your issue refers only to the client side and because the TCP connection close behaviors are tested quite extensively in websockets' test suite.

The server is written in Rust, so I will look into that. Thanks!