Comet is dead, long live websockets

Re:Comet is dead, long live websockets by daleharvey on Wednesday December 16, 2009 @03:09PM (#999608)

the problem isnt the server, http servers right now can serve webpages to any client, its wether the client will allow the connection, as they dont with xhr

from a guess at the fact they specifically say they use the existing same origin policy, they cant, but the confusion is cleared up with a simple test, I will check tomorrow

[ Parent | on HN ]

Re:Comet is dead, long live websockets by mbrubeck on Wednesday December 16, 2009 @03:22PM (#999634)

This is a way for servers to opt in and tell the client to allow cross-domain requests, just like crossdomain.xml or CORS.

I haven't tried it myself with web sockets yet, but I've done some experiments with XHR+CORS (almost the same protocol, except for different names of the response headers) and it does work cross-origin on recent Gecko and WebKit browsers.

UPDATE: Ran a quick test using the current Google Chrome beta for Linux and standalone.py from Google's mod_websocket, and successfully opened a cross-origin WebSocket connection, just as described in the spec. mod_websocket will authorize requests from any origin by default; there's a sample handler included that shows how to reject cross-origin requests on the server.

[ Parent | on HN ]

Re:Comet is dead, long live websockets by daleharvey on Wednesday December 16, 2009 @03:36PM (#999660)

ok cool, if I stand corrected that would be awesome, cheers

[ Parent | on HN ]