They get dropped to xhr-polling even if I have websockets enabled.
I encountered very similar issue on socket.io based app.
On the client, when I force the socket.io transport to be 'websocket' - the browser never receives any updated from the sent websockets handshake (server is a black hole)
However, when I change it to xhr-multipart, all works correctly.
I think it's because nodester uses lib/3rdparty/node-http-proxy.js file to forward requests from port 80 to appropriate app. WebSockets requests are not HTTP requests (although they look very similar) , so they are either stripped (and become invalid in the target app) or not handled at all by the proxy.
I don't have the infrastructure to test this, but it looks as there needs to be some special handling for WebSockets traffic to be forwarded correctly.
This should be working now, can you test it now to make sure?
IT TOTALLY WORKS! Check out http://chat.nodester.com as well as our new blog post http://nodester.tumblr.com/post/3634535277/running-websockets-on-nodester
I confirm, everything works perfectly! Thanks!
It seems the problem has reappeared. socket.io falls back to XHR polling. Possibly related: The chat example at http://chat.nodester.com is stuck at 'connecting'.
... http://chat.nodester.com it's not working!!!