-
Notifications
You must be signed in to change notification settings - Fork 3k
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
IE6 handshake error #413
Comments
forgot to say : socket.io latest version (0.9.5) |
I also detected the same problem too. --- a/socket.io/node_modules/socket.io-client/lib/socket.js
+++ b/socket.io/node_modules/socket.io-client/lib/socket.js
@@ -148,7 +148,9 @@
var xhr = io.util.request();
xhr.open('GET', url, true);
- xhr.withCredentials = true;
+ if (xhr.withCredentials) {
+ xhr.withCredentials = true;
+ }
xhr.onreadystatechange = function () {
if (xhr.readyState == 4) {
xhr.onreadystatechange = empty; |
have same problem.. this patch let avoid error message, but any events in ie6 just not work. my code: server: io.sockets.on "connection", (socket) -> client: in result, i see 'connected' on the server, but not alert in ie. logs: debug - served static content /socket.io.js bad news is that 30% сhinese use ie6, as said my client, and it's necessary for him. building 2 synchronous chats (with socket and without) is nightmare =\ |
Try using JSON-P polling instead of XHR polling |
It works, thanks! |
Karma uses socket.io (more specifically nowadays, engine.io) says it supports browsers "as low as IE 5.5". Ideally that means it works out of the box and not require users hardcode See also karma-runner/karma#983. |
I'm getting a problem while connecting server using IE6 (this problem does not exist under FF 11 & Chrome (v16 or 17) & IE 9) :
Here is the connect system :
this.socket = io.connect('192.168.0.20/chat', {
'reconnect': true,
'reconnection delay': 500,
'max reconnection attempts': 1000,
'port': 8080
});
Under IE6, this result to a syntax error (property not exist, according to IE debug bar) :
//Line 1620
xhr.withCredentials = true;
I also add that's there is no site scripting (both index.html and socket.io are under 192.168.0.20)
The text was updated successfully, but these errors were encountered: