0

I have two different browsers (Chrome and Safari) on the same machine (i.e. same IP), and wonder if it is possible to connect them to the same server both using websocket?

I've tried. Chrome connects fine, but Safari throws an error, complaining:

Error during WebSocket handshake: location mismatch: 
wss://www.mysite.com/sockjs/310/s1a5r_6q/websocket != ws://www.mysite.com/sockjs/310/s1a5r_6q/websocket
sockjs-0.3.js:282Closed transport: websocket SimpleEvent(type=close, code=1006, reason=WebSocket connection broken, wasClean=false)

But I am not sure if this is due to some restriction of one websocket connection per IP address?

MLister
  • 10,022
  • 18
  • 64
  • 92

4 Answers4

4

MLister, you seem to run into sockjs deployment issue. Make sure sockjs server returns wss:// during websocket handshake over https. This is a well-known issue with some sockjs servers - servers don't always know the page is being served over https and return ws:// during handshake.

For example, sockjs-node uses faye-websocket-node code to handle this case is here: https://github.com/faye/faye-websocket-node/blob/master/lib/faye/websocket.js#L40 https://github.com/faye/faye-websocket-node/blob/master/lib/faye/websocket.js#L25-L32

Basically, you must make sure your load-balancer sets 'x-forwarded-proto' header.

Does it make sense?

Marek
  • 3,471
  • 1
  • 16
  • 15
  • while I understand the `x-forwarded-proto` part, what is the logic behind `return (request.connection && request.connection.authorized !== undefined) || (request.socket && request.socket.secure);`, when `x-forwarded-proto` header is not set? – MLister Nov 22 '12 at 13:13
  • 1
    When `x-forwarded-proto` header is not set, faye does best to detect if the connection comes via SSL - but it can only guess. Also, it can detect it only if your SSL termination is done internally by node.js (and not by haproxy, stunnel, etc) – Marek Nov 22 '12 at 14:02
2

There is no technical limitation as far as the WebSocket protocol goes, although there are provisions in the spec for rate limiting outstanding connection attempts per IP address to prevent spamming. With just two I doubt you are running into this problem. There may be other policies that your websocket server has that could restrict this further though.

zaphoyd
  • 2,642
  • 1
  • 16
  • 22
2

wss://www.mysite.com/sockjs/310/s1a5r_6q/websocket != ws://www.mysite.com/sockjs/310/s1a5r_6q/websocket

This indicates the websocket connection went through a proxy that doesn't understand websocket connections. Most likely, it's a reverse proxy on the server end, offloading the SSL overhead from the server behind the proxy. The proxy provided a secure connection to the client but reported the insecurity of the connection from the server to the client. That's not correct.

David Schwartz
  • 179,497
  • 17
  • 214
  • 278
1

It of course is possible, at least if the browser supports the WebSocket API. You don't even need 2 different browsers, you can just open your site in multiple tabs for example in chrome and it should work well.

Van Coding
  • 24,244
  • 24
  • 88
  • 132