-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Never Sees disconnect from client #55
Comments
well. I think this might be an issue with 4.2.9. because if I change the nuGet package to 4.2.4 and below it seems to be working. |
@deniszykov, +1 |
Hi everyone. This one is fixed in 4.2.14 Also don't forget to call |
Super! Updated to 4.2.14 and everything worked, thank you. I think the issue can be closed. |
If I do a javascript ws.close(); from the client, the server never seems to see it.
The earlier version of vtortola 2.2.0.3 seems to work. A .close() on the client, it will trigger a msg = null after the line
String msg = await ws.ReadStringAsync(cancellation).ConfigureAwait(false);
and set the ws.IsConnected to false, taking it to the finally in the try/catch.
The 4.2.9 version just sits there.
I used the simple echoserver code example and it does the same thing. here's my client side code (which I used to test both old and new):
` var noSupportMessage = "Your browser cannot support WebSocket!";
var ws;
`
and my C# code here
` public partial class MainWindow : Window {
public IPEndPoint endpoint; // The IP/Port websocket service is listening on
public WebSocketListener server;
CancellationTokenSource cancellation;
`
As I mentioned, it's pretty much the echo code, and the older version seems to work
The text was updated successfully, but these errors were encountered: