SignalR Web Sockets IIS8 Server 2012 - "Not a Web Socket Request"

I have a site using SignalR (rc1) on IIS8 / Windows Server 2012. It works pretty well, except it seems to be returning to serverSentEvents and I want the web sockets to be really bad.

I see a GET signal / matching with a response of 200: {"URL": "/ signalr", "ConnectionId": "b274f430-7d19-40b8-b448-4ea346042547", "KeepAlive": 15.0, "DisconnectTimeout": 40, 0, "TryWebSockets": true "WebSocketServerUrl": null, "ProtocolVersion": "1.1"}

Then I see a signalr / connect GET with 500 and the exception "Not requesting a web socket":

www.xxxxxx.com/signalr/connect?transport=webSockets&connectionId=56dc6212-387c-43b2-8555-6f8787c9cf17&connectionData=%5B%7B%22name%22%3A%22orderhub%22%7D%2C% 7B% 22name% 3% % 22systemhub% 22% 7D% 5D & TID = 6

Trying to download the link directly gives the following ysod: Not a web socket request

Then it starts using serverSentEvents! Any ideas? Thanks in advance.

+4
source share
1 answer

Our server is located behind the balancer. The loadbalancer only accepts HTTP requests on port 80. I updated the loadbalancer to accept all types of TCP connections on port 80.

Result: WebSockets now work on our site!

+4
source

All Articles