-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chrome 16.0.912.41 beta return code 400 #11
Comments
Would you have any trace from the server? Perhaps traces from Chrome's web developer toolbar as well? |
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. |
On Thu, Dec 15, 2011 at 4:59 PM, Toni Alatalo <
I think it's due to the wrong version that ws4py is supporting. This should |
I can reproduce this in Firefox 8. Headers
|
Damn it. May I ask which version of ws4py you were running? |
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. |
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. |
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. |
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. |
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. |
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 HelloThe text was updated successfully, but these errors were encountered: