Closed martinpitt closed 2 years ago
This actually does happen now, both on logout and when the session container dies.
DEBUG:websockets.client:< CLOSE 1000 (OK) [2 bytes]
DEBUG:websockets.client:= connection is CLOSING
DEBUG:websockets.client:> CLOSE 1000 (OK) [2 bytes]
DEBUG:websockets.client:= connection is CLOSED
and then a clean exit. So let's add a test.
If the /ws websocket gets closed (which usually happens on logout or when the user moves away from the web page), the connector should notice that and exit. If it doesn't, fix it. Add a test that this happens.