No 'Access-Control-Allow-Origin' header is present on the requested resource (socket.io)

[lwansbrough]

I've got a problem which is outlined here: socketio/socket.io-client#641

I've set the correct origins in config/sockets.js but the issue persists for that file alone. Seems to be a bug in socket.io - any workarounds?

[Samstiles]

what about the correct origins in config/cors.js?

[lwansbrough]

They're the same (save for the delimiter).

[lwansbrough]

My origins did not include the port number in config/sockets.js which solved it. The options in config/cors.js still have no effect, I have to set the Access-Control-Allow-Origin header in my middleware.

[adityapatadia]

https://github.com/theoctal/livenote/blob/master/app.js#L11 look here. The issue is essentially solved by setting middleware for express. This makes good example for those who want to know about how to set middleware.

[gCurtisCT]

@adityapatadia I tried that, and it didn't work.

[dcbartlett]

@lwansbrough nailed it. CORS is port sensitive.