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
can't get transports demo to work #4
Comments
No idea - should work without any problems. Do you see any javascript errors? |
wait! i think i'm being an idiot... am running the server on a different machine to the client... |
hm.... some progress, but still no protocols seem to connect. will post detailed error shortly. |
trying with server localhost - websockets works fine, other transports not so good: flashsocket:
fallback to jsonp etc - client side errors: server-side errors:
|
Try grabbing new Tornadio2 from github - I found issue which might prevent Also, support for hybi17 is not in Tornado yet (well, it is, but in Tornado Thanks, On Mon, Nov 7, 2011 at 6:52 PM, hjwp <
|
since websockets works ok with a local server, I thought I'd try it on the server. I modify transports/index.html to use
and I get the following stack trace on attempting to make a websockets connection:
|
sorry if that was all a bit stream-of-consciousness. hope some of it helps. |
What version of Tornado you're using? Thanks for bug report though, if Tornado can't parse websocket handshake, On Mon, Nov 7, 2011 at 7:13 PM, hjwp <
|
Hey, just to let you know I finally got a chance to take another look at this, and upgrading tornado to the latest version worked (we had it pinned at 2.0)... things are looking good! can I make a recommendation for a change to your transports demo: in index.html, line 32: conn = io.connect('http://localhost:8001/', { to become conn = io.connect('http://' + window.location.hostname + ':8001/', { allows server-based test to work transparently... |
Send debug logs when a protocol change is triggered.
seems to serve the main page OK, as well as socket.io.js. when I click "connect" though, it logs "connecting" but doesn't get any further. same in firefox & chromium.
in the server logs, I see:
On the client-side, if I open up the firebug console, I see it tries to make a bunch of ajax GET requests to, eg:
but it doesn't receive a response.
enabling & disabling the various different transport types doesn't seem to make a difference
python 2.6 on debian, FF 7.0.1, Chromium 14.0.835.202 (Developer Build 103287 Linux)
I realise it's early days! any ideas what might be going wrong?
The text was updated successfully, but these errors were encountered: