When trying to establish a web socket connection using SignalR I get an unexpected response error 502.
IE 10 reports: 'WebSocket Error: Incorrect HTTP response. Status code 502, Bad Gateway'
Chrome reports: 'WebSocket connection to 'wss://domain/root/signalr/connect?transport=webSockets&client....' failed: Error during WebSocket handshake: Unexpected response code: 502'
....and after this SignalR then falls back to another transport - so everything still works, but i really want to get this working using web sockets.
When I connect directly to the server, everything works as it should.
I have spend about 3-4 days now searching for how to get SignalR 2.2.1 working with an IIS 8.5, in WindowsServer 2012 R2, ARR 3.0.
I am using SSL/https - I have sticky sessions configured, same machine key on all my back end servers.
I have setup a test system, that has only a single server behind a single ARR load balancer, I have tried every suggestion that I can find but I still cant find a solution - or for that matter anyone indicating that they have successfully configured this
even though Microsoft claim it is support "with no extra config".
Can anyone point me towards a guide or reference for getting this working ?
What other steps should I be trying to debug this configuration ?
Can anyone confirm it even works - or even that it does not work ?
I asked on stackoverflow but so far haven't had even a single response after a week - I really like ARR & URL Rewrite, I have used it for quite a few years now with millions of requests a day going through it, but with the lack of any documentation or assistance
for ARR in general I am having to seriously consider finding another solution ....
https://stackoverflow.com/questions/44092063/signalr-websocket-fails-with-unexpected-response-code-502-iis-8-5-arr-3-0
If anyone can actually help me get this working I will take the time to write some documentation on how to make it work - step by step, with all the source code for a test SignalR app, all the configuration for IIS, ARR, UrlRewrite - and post it all
on github, microsoft docs or somewhere that others can find !