JS client attempts to fallback to other transports if WebSockets is exclusively specified even if server doesn't support WebSockets #2294

Closed
DamianEdwards opened this Issue Jul 15, 2013 · 1 comment

Projects

None yet

2 participants

Owner

If the web server doesn't support WebSockets (returns TryWebSockets:false in the negotiate response), and the connection is started explicitly stating only WebSockets as the transport, the client will continue to try and start the connection with other transports.

I discovered this because my home desktop had sort sore of IIS Express misconfiguration which resulting in WebSockets not working in ASP.NET (despite it being Windows 8) and it caused some of the JS unit tests to fail strangely.

@gustavo-armenta gustavo-armenta added a commit that referenced this issue Oct 10, 2013
@gustavo-armenta gustavo-armenta #2294 JS client attempts to fallback to other transports if WebSocket…
…s is exclusively specified even if server doesn't support WebSockets
ef63453
@gustavo-armenta gustavo-armenta added a commit that referenced this issue Oct 10, 2013
@gustavo-armenta gustavo-armenta #2294 JS client attempts to fallback to other transports if WebSocket…
…s is exclusively specified even if server doesn't support WebSockets
c725b11
Contributor

automated new tests on FallbackConnectionFacts.js verify the fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment