Bugs Fixed
- /start requests deadlock when the PreSendRequestHeaders event is set (#3116)
- ASP.NET Hub.OnDisconnected not called when .NET client disconnects due to Internet connectivity/process killed (#3115)
- SignalR 2.1 - JavaScript error: Refused to execute script...because MIME type ('application/json') is not executeable... (#3110)
- JS Client - No transport can be initialized if /start takes too long to complete (#3104)
- Unexpected lock reentry in HubConnection.ClearInvocationCallback (#3101)
Breaking Changes
OnDisconnect parameterless overload removed
In 2.1.0 we added an overload of OnDisconnect on PersistentConnection and Hub that takes a boolean indicating whether the disconnect from the client was due to a timeout or not. In making this change we also changed when the existing overload (without the parameter) was called. These changes together resulted in applications not always being called when a client disconnects in a way they were used to expecting. We're resolving this in 2.1.1 by removing the original overload (the parameterless one). OnDisconnect will now always be called when a client disconnects and the flag passed indicates whether it was due to a timeout or not.