KnowledgeHub
Questions
Tags
Users
Search
Alex Rivera
|
Logout
Edit Question
Title
Body
I upgraded to .NET 4.5, now SignalR seems insistent on using WebSockets in Firefox/Chrome - even though I'm only on Windows 7 which doesn't have a WebSocket Server. The request obviously fails: Firefox can't establish a connection to the server at ws://www.site.local/signalr?connectionData= How do I force SignalR to forget about Websockets and use Long Polling, or is there a way of setting up Websockets for Windows 7 that I'm missing? Update.... I'm using SignalR 0.4: <package id="SignalR" version="0.4.0" /> <package id="SignalR.Hosting.AspNet" version="0.4.0.0" /> <package id="SignalR.Js" version="0.4.0.1" /> <package id="SignalR.Server" version="0.4.0.0" /> <package id="SignalR.StructureMap" version="0.4.1" />
Tags (comma-separated)
Save Edits
Cancel