I have an ASP.NET MVC 4 app (.NET 4.5) and SIgnalR works fine with forms-based authentication (hosted via IIS/IIS Express)
As soon as I change the app to windows-int
I too was experiencing this error, but only when developing locally using http
; I think Chrome doesn't like unsecured ws://
connections. Once I deployed to server with secure https
connection, the WebSocket connection was upgraded to wss://
, and Chrome stopped complaining, worked fine with WebSockets--didn't have to fall back to other transport.
tl:dr; Make sure to use https
for your site.