Compressed bit must be 0 if no negotiated deflate-frame extension

[AndreasBackx]

I recently set my testing up on my website which then connects to the server with socket.io, connection is fine and stuff. But it connects, gives an error, runs the event error, disconnect, connecting and then tries again. This is my debug:

Event: connect
Compressed bit must be 0 if no negotiated deflate-frame extension :1
Event: error
Event: disconnect
Event: connecting
Event: connect
...

I didn't had this issue when trying this out on my localhost, I Googled around and didn't find much help, except someone that uses Python and got a problem with it too. Here's the link.

Also, I seem to be the only person having this problem and it's not only with my chat. My friend's chat that uses socket.io has the same problem for me, but not for anyone else.

[fulopattila122]

I also saw this error today. But it only happens with Chrome 25 on one Windows 7 laptop. Chrome 25 on my macbook doesn't display this error.

[vladberteanu]

I'm seeing this error for a very small percentage of our users, but I wasn't able to reproduce it. One of the users sent me this error line from Chrome console.

WebSocket connection to 'ws://practice.talentbuddy.co/socket.io/1/websocket/4iVZDvIT_ofwVcDU0AN7' failed: Compressed bit must be 0 if no negotiated deflate-frame extension

We are running nodejs, express 3, socket.io 0.9 behind haproxy 1.4.

Any ideas why is this happening?

[fulopattila122]

I see that it might be caused by a proxy at the ISP as well. I realized that for example Vodafone (at least in Romania) is heavily using proxies and this causes websockets to fail or fall back to xhr in certain circumstances.