SignalR websocket closure not handled well - am I missing something? #409
-
I have a test setup, all localhost, consisting of a reverse-proxy service, a SignalR service, and a SignalR client: Client -> reverse-proxy -> service. Everything works great until I hit Ctrl+C on my client. An exception is generated in the reverse proxy, but the connection to the SignalR service is maintained, and my service keeps pushing updates back through the connection (or is trying to). My expectation was that when the websocket was closed from the client, the reverse proxy would close the websocket to the server. Any help is welcome! Note that if I quit the client cleanly, it does disconnect cleanly all the way back to the service. The exception I see is:
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
I'm working on this now over at #406. I plan to get it into preview 5. |
Beta Was this translation helpful? Give feedback.
-
Re-tested today with preview 5, and all looks good. Thanks again! |
Beta Was this translation helpful? Give feedback.
I'm working on this now over at #406. I plan to get it into preview 5.