Node.js 在Firefox中,Socket.io返回到xhr
我的应用程序使用Node.js和Socket.io。它可以正常工作,但当我断开与internet的连接时,Socket.io会返回到xhr,但仅在Firefox和chrome上就可以正常工作 这是我的调试消息:Node.js 在Firefox中,Socket.io返回到xhr,node.js,websocket,socket.io,Node.js,Websocket,Socket.io,我的应用程序使用Node.js和Socket.io。它可以正常工作,但当我断开与internet的连接时,Socket.io会返回到xhr,但仅在Firefox和chrome上就可以正常工作 这是我的调试消息: info - socket.io started Express server listening on port 3000 development GET /connexion 200 38ms - 882 POST /connexion 302 5ms - 64 GET /jeu
info - socket.io started
Express server listening on port 3000 development
GET /connexion 200 38ms - 882
POST /connexion 302 5ms - 64
GET /jeu 200 8ms - 583
debug - client authorized
info - handshake authorized UTHMxCJEKx-DC3sSf57M
debug - setting request GET /socket.io/1/xhr-polling/UTHMxCJEKx-DC3sSf57M?t=1365791206086
debug - setting poll timeout
debug - client authorized for
debug - clearing poll timeout
debug - xhr-polling writing 1::
debug - set close timeout for client UTHMxCJEKx-DC3sSf57M
debug - xhr-polling received data packet 1::/jeu/Jeu1
s:B2ZSTca4rYyle+ooJCY5/Z+d.xuW1XrVrU+IG0UpLvs5q88hm6Nr83SOwr7fpOjfPhbM
B2ZSTca4rYyle+ooJCY5/Z+d
debug - client authorized for /jeu/Jeu1
debug - setting request GET /socket.io/1/xhr-polling/UTHMxCJEKx-DC3sSf57M?t=1365791206116
debug - setting poll timeout
debug - clearing poll timeout
debug - xhr-polling writing 1::/jeu/Jeu1
debug - set close timeout for client UTHMxCJEKx-DC3sSf57M
debug - discarding transport
debug - cleared close timeout for client UTHMxCJEKx-DC3sSf57M
newPlayer: hamou92
debug - broadcasting packet
debug - setting request GET /socket.io/1/xhr-polling/UTHMxCJEKx-DC3sSf57M?t=1365791206203
debug - setting poll timeout
debug - discarding transport
debug - cleared close timeout for client UTHMxCJEKx-DC3sSf57M
这是Firebug向我展示的:
Firefox ne peut établir de connexion avec le serveur à l'adresse ws://localhost:3000/socket.io/1/websocket/_uQklvPYeYn-_BNg-WDa.
this.websocket = new Socket(this.prepareUrl() + query); socket.io.js (ligne 2371)
您使用的是哪个firefox版本?检查这里是否支持websocket我正在使用Firefox的最新版本,我刚刚更新了它。我的UbuntuI版本是20.0,我刚刚更新了我的Ubuntu,这个问题被忽略了。