From 49bed2e3e2bc6994f8fc542b2c63367913baa16c Mon Sep 17 00:00:00 2001 From: Rick Anderson Date: Thu, 20 Sep 2018 12:46:09 -1000 Subject: [PATCH] Update troubleshooting.md --- .../signalr/overview/testing-and-debugging/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnet/signalr/overview/testing-and-debugging/troubleshooting.md b/aspnet/signalr/overview/testing-and-debugging/troubleshooting.md index 8a54da41ae..e1ec5ababc 100644 --- a/aspnet/signalr/overview/testing-and-debugging/troubleshooting.md +++ b/aspnet/signalr/overview/testing-and-debugging/troubleshooting.md @@ -151,7 +151,7 @@ A connection in a .NET client application that uses Domain security may fail if ## Configuring IIS websockets to ping/pong to detect a dead client -SignalR servers don't know if the client is dead or not and they rely on notification from the underlying websocket for connection failures, that is, the OnClose callback. One solution to this problem is to configure IIS websockets to do the ping/pong for you. This ensures that your connection will close if it breaks unexpectedly. For more information see [this stackoverflow post](http://stackoverflow.com/questions/19502755/websocket-clients-state-not-changing-on-network-loss). +SignalR servers don't know if the client is dead or not and they rely on notification from the underlying websocket for connection failures, that is, the `OnClose` callback. One solution to this problem is to configure IIS websockets to do the ping/pong for you. This ensures that your connection will close if it breaks unexpectedly. For more information see [this stackoverflow post](http://stackoverflow.com/questions/19502755/websocket-clients-state-not-changing-on-network-loss).