chrome 16.0.912.41 beta return code 400

[baoming]

os: mac osx 10.6.2
chrome: 16.0.912.41 beta
ws4py: master

issue:

when use test with echo client , chrome console report server return 400 status code.

client test code:

<script type="text/javascript"> window.onload = function() { var ws_uri = "ws://localhost:9000"; if ("WebSocket" in window) { webSocket = new WebSocket(ws_uri); } else { // Firefox 7/8 currently prefixes the WebSocket object webSocket = new MozWebSocket(ws_uri); } webSocket.onmessage = function(e) { console.log("Got echo: " + e.data); } } </script>

Autobahn WebSockets Echo Test

Send Hello

[Lawouach]

Would you have any trace from the server? Perhaps traces from Chrome's web developer toolbar as well?

[antont]

I get this now with Chrome 15 too. Worked I think in some earlier 15, and in 14. Hasn't worked with 16 ever for me yet.

Tested now with chromes 15.0.874.121 and with 16.0.91.63 (m on win, without m on mac) to which it seemed to update.

Server shows just a normal log entry with "GET / HTTP/1.1" 400 120 0.000241

Am using the gevent server and ws4py master.

[Lawouach]

On Thu, Dec 15, 2011 at 4:59 PM, Toni Alatalo <
reply@reply.github.com

wrote:

I get this now with Chrome 15 too. Worked I think in some earlier 15, and
in 14. Hasn't worked with 16 ever for me yet.

Tested now with chromes 15.0.874.121 and with 16.0.91.63 (m on win,
without m on mac) to which it seemed to update.

Server shows just a normal log entry with "GET / HTTP/1.1" 400 120 0.000241

Am using the gevent server and ws4py master.

I think it's due to the wrong version that ws4py is supporting. This should
be fixed in my next release soonish.

• Sylvain
  http://www.defuze.org
  http://twitter.com/lawouach

[nettok]

I can reproduce this in Firefox 8.

Headers

Solicitud de URL:
    http://localhost:9000/

Solicitud de Método:
    GET

Código de estado:
    HTTP/1.1 400 Bad Handshake



Solicitud de encabezados
    15:00:41.769

  Accept:text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
  Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.7
  Accept-Encoding:gzip, deflate
  Accept-Language:es-GT,es;q=0.8,en-us;q=0.5,en;q=0.3
  Cache-Control:no-cache
  Connection:keep-alive, Upgrade
  Host:localhost:9000
  Pragma:no-cache
  Sec-WebSocket-Key:ZZZmL1iDefZgRQwzD3s8tg==
  Sec-WebSocket-Origin:null
  Sec-WebSocket-Version:8
  Upgrade:websocket
  User-Agent:Mozilla/5.0 (Ubuntu; X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0


Encabezados de respuesta
    Δ2ms

  Content-Length:29Date:Fri, 30 Dec 2011 21:00:41 GMT

[Lawouach]

Damn it. May I ask which version of ws4py you were running?

[nettok]

According to "pip freeze" I am running ws4py==0.1.5 and gevent==0.13.6

The client test code is the same as baoming. Taken from the Autobahn tutorial.

[antont]

There were apparently some commits to the protocol code in early January, does some browser work now? I tried to test current but so far couldn't connect with Firefox or Chrome.

[Lawouach]

Well the example/echo_cherrypy_server.py module does work well on my Chrome 16.0.912.77 on Linux. Could you be a little more precise about the error you get and what you are running.

[antont]

That (the cherrypy example) works for me to, thanks for info.

I was testing with the gevent server that we've been using, and the error seemed to be the same as earlier in these reports. Will test again and ensure that got it really updated etc. and look deeper when get the chance, perhaps later today or within a couple of days.

[antont]

our gevent using server does work too, I just accidentally used an old version of ws4py with that earlier - thanks again, and I suppose this issue can closed now.