Last post Aug 08, 2014 11:32 AM by kahlua
Aug 05, 2014 05:21 PM|kahlua|LINK
I have signalr hub client/server code working with redis as a backplane. In a single worker process, websocket enabled browsers are able to complete the handshake. However, once I bump up the number of worker processes, upon handshake, client error of "
Error during WebSocket handshake: Unexpected response code: 400 " spits up. I have subscribed to the event key in redis and do see messages being inserted. Is there anything else that I need to configure?
Aug 08, 2014 05:07 AM|Fuxiang Zhang - MSFT|LINK
Thanks for your post.
According to your description, I see you want to use the redis to scale your signalR application.
For hos to do it you can follow below example.
client error of " Error during WebSocket handshake: Unexpected response code: 400 "
As for the error above, I suggest you use a SSL (Https) in your signalR application. As mentioned, " Websocket over plain http
is vulnerable to proxies in the middle (often transparent) operating at the http layer breaking the connection."
Aug 08, 2014 11:32 AM|kahlua|LINK
Thanks. I've followed the steps in the above article when I set it up. Using the Redis dependency, it works in a single process and I do see messages in Redis. Also, I am using an SSL connection, a valid SSL certificate. The error occurs only when I increase
the worker process to more than 1.