daohualiuxiang
/
AspNetCore.Docs
mirror of https://github.com/dotnet/AspNetCore.Docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update troubleshooting.md

pull/8648/head
Rick Anderson 2018-09-20 12:46:09 -10:00 committed by GitHub
parent 4f5fa6239d
commit 49bed2e3e2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
aspnet/signalr/overview/testing-and-debugging/troubleshooting.md
View File

@ -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 ## 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).
<a id="other"></a> <a id="other"></a>