XHR fallback on Localhost

[Andrew Seddon]

I'm having some trouble getting anything other than XHR to localhost
on OS X Lion in Chrome Dev and FF4, Safari talk's web sockets fine.

now 0.7.3
socket 0.7.7

Express server listening on port 8081, environment: development
Using connect 1.6.0, Express 2.4.3, Jade 0.10.4
info - socket.io started
debug - served static /socket.io.js
debug - client authorized
info - handshake authorized 855137317355647265
debug - setting request GET /socket.io/1/websocket/
855137317355647265
debug - set heartbeat interval for client 855137317355647265
warn - websocket connection invalid
info - transport end
debug - set close timeout for client 855137317355647265
debug - cleared close timeout for client 855137317355647265
debug - cleared heartbeat interval for client 855137317355647265
debug - client authorized for
debug - client authorized
info - handshake authorized 6366976092090266715
debug - setting request GET /socket.io/1/xhr-polling/
6366976092090266715?t1312036500931
debug - setting poll timeout
debug - client authorized for
debug - clearing poll timeout
debug - xhr-polling writing 1::
debug - set close timeout for client 6366976092090266715
debug - setting request GET /socket.io/1/xhr-polling/
6366976092090266715?t1312036500939
debug - setting poll timeout
debug - clearing poll timeout

[Steve Wang]

Chrome dev uses a new websocket protocol that isn't backwards-
compatible with the old one. This is a known bug, and we're working to
resolve this as quickly as possible.

[Andrew Seddon]

Great, thanks Steve.

[maxi]

The same problem with Chrome 14.0.835 ..

The bug has been fixed?

Thanks

[Eric Zhang]

Yes, by upgrading to latest NowJS (0.7.5) and socket.io (0.8.4), this issue has been fixed.

Eric

--
Co-Founder @ Flotype, makers of NowJS

[maxi]

Upgrade and works fine with firefox 6 and chrome 14

thanks
Maxi