Home/ Questions/Q 8169707
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-06T20:55:48+00:00

I’am using PHP Websocket server by lemmingzshadow ( web ). Everything worked just fine

  • 0

I’am using PHP Websocket server by lemmingzshadow (web). Everything worked just fine till now.

After update to chrome 20, if I want to do handshake with server it ends with this error

Error during WebSocket handshake: Sec-WebSocket-Protocol mismatch

Headers from chrome 20

GET /demo HTTP/1.1
Upgrade: websocket
Connection: Upgrade
Host: gomokulive.eu:8001
Origin: http://www.gomokulive.eu
Sec-WebSocket-Key: s+AMQQu4Q10xH2AKy49byg==
Sec-WebSocket-Version: 13
Sec-WebSocket-Extensions: x-webkit-deflate-frame

Headers sent back:

HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: dMCVYKkF5VRrIouWFW7EYdvfD28=
Sec-WebSocket-Protocol: demo

I think problem is with “Sec-WebSocket-Extensions: x-webkit-deflate-frame” header from Chrome 20.

Any idea how to get it working again?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The server is violating the WebSocket protocol. It’s likely that Chrome is just adhering to the standard more correctly in version 20 and that is revealing a bug in the server.

    The problem is that the server is sending back a "Sec-WebSocket-Protocol" header in the response but this is only legal if the client sends the same header in the request. If the client does not send the Sec-WebSocket-Protocol then the server should omit the header in the response.

    See the /subprotocol/ description on page 22 in Section 4.2.2 of rfc6455

    • 0