title: Websockets anomaly in Chrome 19 (latest beta)
body: <p>I've been using websockets without an issue for months to communicate between Chrome and my localhost app. Suddenly, with the latest version of Chrome, data is not going through cleanly.</p>
  
  <p>In the Chrome extension's javascript, the relevant part of the code is:</p>
  
  <pre><code>window.ws = new WebSocket("ws://localhost:13000/");
  
  window.ws.onopen = function () {
      window.ws.send('GO');
  </code></pre>
  
  <p>In my C# app:</p>
  
  <pre><code>string msg = ASCIIEncoding.UTF8.GetString(buffer);
  Debug.WriteLine(msg);
  </code></pre>
  
  <p>For months this worked fine and I would get "GO" back out day in, day out. Now what I'm getting on the receiving buffer is 4 bytes <strong><code>{114,247,7,0)</code></strong> which does not translate to "GO" in any encoding I can find. Anyone have any idea what could be happening? I'm bemused as I have not touched either end of code (chrome or listener).</p>
  
  <p>Cheers!</p>
  
  <p>PS: The full Chrome Version 19.0.1084.15 beta-m</p>