CODEWITHSUNDEEP
google-chromewebsocket
user3450613
user3450613

Reputation: 21

Chrome WebSocket returns "unexpected error 200"

It looks like a WebSocket creation problem, which should not be happening with chrome. I tested it with different browsers (including chrome) from different machines (same OS same NW config) and it was OK.

How is this even possible?

Upvotes: 1

Views: 459

Answers (1)

mork
mork

Reputation: 1863

I was struggling with a similar issue with chrome and safari about 3 years ago. In my case it was, at the end, an issue of WebSockets versions

Basically there were 2 main protocols of WebSockets: Hixi and Hybi, Hybi becoming the successor

You mentioned that with the same config one chrome browser works and one gives you that error. Can you please check the versions of Chrome on both scenarios? I know its a long shot, but if the "broken" one is running a very old version, say bellow 14 from around 2011, according to the chrome version history - this just might be it

BTW, which server are you using?

Upvotes: 2

Related Questions