Cross domain errors when current version that uses socket.io version 1.0.5

1

We are getting the No Access-Control-Allow-Origin error when Erizo.js makes
a call to the ErizoController.js when using the latest Licode version.
Socket.io 1.0.5. has replaced 0.9.6 which we had been using without cross
domain error problems. I have tried all sorts settings in my express based
server application based on the new origin settings calls in socket.io
without any luck. Any one else having this problem and a fix.

Thanks

Wilbert Jackson

2

the erizoController on the server is not compatible with socket.io > 1.0.

You will need to edit it and change all the io.sockects.socket ( xxxxx
).emit
into
io.sockects.connected[ xxxx].emit

and then force erizonController to use io sockects > 1.0. The install
install 0.9.6 version of socket.io.

It would be great if that could be put into the source and if the socket.io
could be removed from erizo.js client file. Would be much cleaner in my
opinion.On Friday, June 5, 2015 at 4:49:22 AM UTC-4, Cracker F wrote:

I have the same problem and no solution at the moment.
Do you have found out something usefull yet ?

I posted this as issue on github:
Basic Example not working: Cross-Origin · Issue #303 · lynckia/licode · GitHub

Am Mittwoch, 18. Juni 2014 19:34:32 UTC+2 schrieb Wilbert Jackson:

We are getting the No Access-Control-Allow-Origin error when Erizo.js
makes a call to the ErizoController.js when using the latest Licode
version. Socket.io 1.0.5. has replaced 0.9.6 which we had been using
without cross domain error problems. I have tried all sorts settings in my
express based server application based on the new origin settings calls in
socket.io without any luck. Any one else having this problem and a fix.

Thanks

Wilbert Jackson

3

I have the same problem and no solution at the moment.
Do you have found out something usefull yet ?

I posted this as issue on github: Issues · lynckia/licode · GitHub Mittwoch, 18. Juni 2014 19:34:32 UTC+2 schrieb Wilbert Jackson:

We are getting the No Access-Control-Allow-Origin error when Erizo.js
makes a call to the ErizoController.js when using the latest Licode
version. Socket.io 1.0.5. has replaced 0.9.6 which we had been using
without cross domain error problems. I have tried all sorts settings in my
express based server application based on the new origin settings calls in
socket.io without any luck. Any one else having this problem and a fix.

Thanks

Wilbert Jackson