asp.net - Signalr: WebSocket connection to 'wss://***': Error during WebSocket handshake: Unexpected response code: 502 -


i use signalr v2.0.2 js-client (websocket transport) on asp.net 4.5 site , iis-8 (websockets enabled). after load testing (using selenium) can see next error in console of browser (* our domain name).

[20:23:46 gmt+0400 (russian standard time)] signalr: connecting websocket endpoint 'wss:///connect?transport=websockets&connection…6gkcou%3d&state=1&connectiondata=%5b%7b%22name%22%3a%22chat%22%7d%5d&tid=1'. projects-fk0zhh5_zuo_6i0z725jug2.js?ver=7.627:54 websocket connection 'wss:///signalr/connect?transport=websockets&connection…6gkcou%3d&state=1&connectiondata=%5b%7b%22name%22%3a%22chat%22%7d%5d&tid=1' failed: error during websocket handshake: unexpected response code: 502

i error after finished load testing. never saw error , don't know reason of this. can resolved application restart.

check out: http://www.infoq.com/articles/web-sockets-proxy-servers

this due not using https (ssl). websocket on plain http vulnerable proxies in middle (often transparent) operating @ http layer breaking connection.

this common on cellular networks, or office networks may use multiple wireless connections proxy spreads http requests across connections.

the way avoid use ssl time - gives websocket best chance of working.


Comments

Popular posts from this blog

android - Get AccessToken using signpost OAuth without opening a browser (Two legged Oauth) -

org.mockito.exceptions.misusing.InvalidUseOfMatchersException: mockito -

google shop client API returns 400 bad request error while adding an item -