v1.0.0 upgrade fails with "handshake error: bad \"Upgrade\" header

[rusenask]

Hi, trying out the new version all ws requests fail with handshake error: bad \"Upgrade\" header.

[rusenask]

Update: I suspect it's my problem, as after downgrade it still misbehaves, maybe some middleware :|

[jjhesk]

handshake error: bad "Upgrade" header
still i have the same problem now.. can you fix that? @gobwas

[gobwas]

@jjhesk Hi, if this is a bug inside ws, for sure I can. Could you provide more details on your problem? Thanks.

[amaresh494]

@gobwas Hello, I'm getting the same error, when I connect to the WebSocket server using NGINX proxy. Here's how my code looks like,

and NGINX configuration is as below,

location /wsapp/ {
    proxy_pass http://localhost:8080;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
    proxy_set_header Host $host;
}

The problem is when I try connecting to the WebSocket server through Nginx proxy, I'm getting the "handshake error: bad "Upgrade" header error on the WebSocket server side.

Please help!

[cristaloleg]

What is the value of Upgrade header?

[Kiura]

I still am getting this error in May 2022 (v1.1.0)