We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm using the latest source, a clone from yesterday, just after the latest release. My Chrome version is 6.0.472.63 and Firefox version is 3.6.10.
I forced flashsocket to be used just to test it, using the chat server example included in the repository. In chat.html, I did this:
var socket = new io.Socket(null, { port: 8124, rememberTransport: false, transports: [ 'flashsocket' ] });
Both Chrome and Firefox hang at "Connecting..". This is the error I see in the console for Chrome:
No transport available socket.io/socket.io.js:799
Nothing shows up in the Firebug console on FF. I haven't tested on IE.
Things work fine if I don't force flashsocket, using websocket for Chrome and xhr-multipart on Firefox.
The text was updated successfully, but these errors were encountered:
[revert] "[fix] Enable to utf8-decode string payloads (#88)" (#91)
bffb63e
This reverts commit 278a7e4.
No branches or pull requests
I'm using the latest source, a clone from yesterday, just after the latest release. My Chrome version is 6.0.472.63 and Firefox version is 3.6.10.
I forced flashsocket to be used just to test it, using the chat server example included in the repository. In chat.html, I did this:
Both Chrome and Firefox hang at "Connecting..". This is the error I see in the console for Chrome:
Nothing shows up in the Firebug console on FF. I haven't tested on IE.
Things work fine if I don't force flashsocket, using websocket for Chrome and xhr-multipart on Firefox.
The text was updated successfully, but these errors were encountered: