-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JS Same Origin Policy Issue #5
Comments
Same issue here |
Can one or both of you look at this stackoverflow question? Since I'm not experiencing this problem I can't offer much help. |
I'm seeing it now too. Investigating. |
If I can assume that you are seeing this in Chrome, then this is a problem in Faye and a fix has been submitted faye/faye issue #213. I don't have complete confidence this is a silver bullet, however, because I read here that the Cedar stack does not officially support the WebSockets protocol currently. Having said that, besides a messy console I haven't seen a downside and my app seems to function normally otherwise. I personally use Heroku only for development and wouldn't go into production with a faye server hosted there at this time. I'll leave this issue open until the Faye code is merged and I can look at this again. |
Hello,
This is working as expected, yet I'm getting the following errors in my console log:
• WebSocket connection to 'ws://our-faye-server.herokuapp.com/faye' failed: Unexpected response code: 400
• XMLHttpRequest cannot load http://our-faye-server.herokuapp.com/faye. Origin http://our-app-url.com is not allowed by Access-Control-Allow-Origin.
It seems to have something to do with the same origin policy. Do you have a fix for this already?
Thanks!
The text was updated successfully, but these errors were encountered: