0267695656
We need to close the connection if there is an exception when writing to the transport on the server side. Currently if an exception happens it leaves the connection in an unsable state - after the exception no messages from the server will be sent to the client because the writing loop is terminated. Ignoring the message could cause hangs on the client side since we can fail while writing a completion message. In this case if the client is awaiting the invocation it will hang because the task will never be completed. |
||
|---|---|---|
| .. | ||
| Internal | ||
| CancellationDisposable.cs | ||
| DefaultHubActivatorTests.cs | ||
| DefaultTransportFactoryTests.cs | ||
| EchoEndPoint.cs | ||
| EndToEndTests.cs | ||
| HubEndpointTests.cs | ||
| HubReflectionHelperTests.cs | ||
| MapSignalRTests.cs | ||
| Microsoft.AspNetCore.SignalR.Tests.csproj | ||
| SignalRDependencyInjectionExtensionsTests.cs | ||
| Startup.cs | ||
| TestClient.cs | ||
| UncreatableHub.cs | ||
| WebSocketsTransportTests.cs | ||