-
Notifications
You must be signed in to change notification settings - Fork 114
Unexpected end of stream - Should be close? #63
Comments
How did you hit this? |
I think hard disconnects/dirty close rather than close messages; can recreate easily by connecting via websockets with a client then terminating it (the client) |
It didn't do anything untoward - other than being very messy for the error log |
Feels a bit like this sort of state: https://github.com/SignalR/SignalR/blob/3a219c101587333d562f04f30903d50ad9773e1c/src/Microsoft.AspNet.SignalR.Core/Owin/WebSockets/WebSocketHandler.cs#L237 Is a disconnect rather than an error |
Oh so it's behaving as expected, it's just noisy. A disconnect is an error in the WebSocket protocol, it's just not a very interesting one. We can check the flow and see if it can be simplified. |
Yea, agreed, but its a bit like someone disconnecting mid http download - probably don't care too much; whereas a |
Moving out, though would be happy to accept a PR :) |
I get the same error. I read most of the links but I could not understand how to handle it. I publish my application and send data to the client. it works. then I disconnect the client without closing browser (like unplugging network cable) and try sending again it fails. I use try catch and looks ok but then I get this error in log file. should I detect the users who are not used to close their browsers and block them from the application.. I add this link here because of GitHub does not let vote down |
The text was updated successfully, but these errors were encountered: