Open dahmadjid opened 2 months ago
Hi, is there a way to see the issue happening without the close/disconnect ? The socket is still open somewhere using netstat for example ? Regards,
Hi, No I just wanted to close the websocket myself in case of application-level errors (instead of sending a special message using ->send())
Adding something like this to the websocket_session class should do the job i believe.
void close() { _websocket.close(beast::websocket::internal_error); _route.disconnect(_ws_context); }