Databases
StackOverflow2013
Postsdbo
POCannot get websocket connection to work in Chrome 19
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCannot get websocket connection to work in Chrome 19
    primarykey
    data
    text
    <p>I have a websocket client/server that works perfectly with Firefox and Chrome 18. It does not work with Chrome 19 beta. I suspect it is due to this browser now using a deflate-frame extension which my server doesn't support.</p> <p>Chrome 19 beta is sending this in its handshake: "Sec-WebSocket-Extensions: x-webkit-deflate-frame"</p> <p>I have my server sending back: "Sec-WebSocket-Extensions: "</p> <p>But either this isn't the proper way to reject the extension or there is something else wrong that I'm not catching. This is the only thing in the handshake that is different from what I see coming from the working browsers.</p> <p>Edit: Here is some additional information. These are the handshakes as captured by Wireshark.</p> <hr> <p>The handshake using Firefox 12:</p> <p>GET /chatserver HTTP/1.1<br> Host: (omitted for this post)<br> User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20100101 Firefox/12.0<br> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,<em>/</em>;q=0.8<br> Accept-Language: en-us,en;q=0.5<br> Accept-Encoding: gzip, deflate<br> DNT: 1<br> Connection: keep-alive, Upgrade<br> Sec-WebSocket-Version: 13<br> Origin: (omitted for this post)<br> Sec-WebSocket-Key: 2TKm4ozUQdNP17Lobt7IBg==<br> Pragma: no-cache<br> Cache-Control: no-cache<br> Upgrade: websocket </p> <p>HTTP/1.1 101 Switching Protocols<br> Upgrade: websocket<br> Connection: Upgrade<br> Sec-WebSocket-Accept: pSUB3BT9YUUd9n3mOeWY/1uVqJE= </p> <hr> <p>The handshake using Chrome 18:</p> <p>GET /chatserver HTTP/1.1<br> Upgrade: websocket<br> Connection: Upgrade<br> Host: (omitted for this post)<br> Origin: (omitted for this post)<br> Sec-WebSocket-Key: zuHLEC8pGvAMadarhCLXFA==<br> Sec-WebSocket-Version: 13 </p> <p>HTTP/1.1 101 Switching Protocols<br> Upgrade: websocket<br> Connection: Upgrade<br> Sec-WebSocket-Accept: LMBSq6Bk9Kiv+zAbQlAL899pfzc= </p> <hr> <p>The handshake using Chrome 19:</p> <p>GET /chatserver HTTP/1.1<br> Upgrade: websocket<br> Connection: Upgrade<br> Host: (omitted for this post)<br> Origin: (omitted for this post)<br> Sec-WebSocket-Key: TbwnVcuUiqGgZn7hxvxzvQ==<br> Sec-WebSocket-Version: 13<br> Sec-WebSocket-Extensions: x-webkit-deflate-frame </p> <p>HTTP/1.1 101 Switching Protocols<br> Upgrade: websocket<br> Connection: Upgrade<br> Sec-WebSocket-Accept: D45BJ+Vfydy1Upcs3Hze/nuiaS8=<br> Sec-WebSocket-Extensions: </p> <hr> <p>All server responses have \r\n line-endings and include an extra \r\n at the end of message.</p> <p>FF12 and Chrome18 work -- <strong>Chrome19 does not work</strong>. In Chrome19, the very next packet after the server handshake response is a FIN/ACK. The connection is closed.</p> <p>nb. I have also tried using a hyphen as the Sec-WebSocket-Extensions value but that didn't work either.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAaron
    1. USAaron
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCannot get websocket connection to work in Chrome 19
      1. USigorw
      1. VTFavorite
    2. VO
      singulars
      1. POCannot get websocket connection to work in Chrome 19
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POCannot get websocket connection to work in Chrome 19
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload