Client behind proxy without websocket support upgrades to websocket

[svestka]

If a client is behind proxy without websocket support, it upgrades connection from polling to websockets anyway, which leads to unexpected hangs.

How to reproduce with nginx for example:
Just create simple proxy without websockets support and point engine.io-client to port 80 (or whatever port your nginx server listen to)

location /engine.io/ {
    proxy_set_header   X-Real-IP         $remote_addr;
    proxy_set_header   X-Forwarded-For   $proxy_add_x_forwarded_for;
    proxy_set_header   X-Forwarded-Proto $scheme;
    proxy_set_header   Host              $http_host;
    proxy_set_header   X-NginX-Proxy     true;
    proxy_set_header   Connection "";
    proxy_read_timeout 86400;
    proxy_http_version 1.1;
    proxy_pass http://localhost:3000/engine.io/;
}

[rauchg]

@aeosynth do you think this is the same issue as socketio/engine.io#177 ?

[plievone]

Fixed by socketio/engine.io#222 ?

[svestka]

I'm not able to reproduce the problem anymore, seems fixed.

I will keep an eye on it

[rauchg]

We definitely tested this. Closing. Thanks @peterslivka