Skip to content
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

A workaround for the "A wildcard '*' cannot be used in the 'Access-Control-Allow-Origin' header..." issue? #44

Open
csleary opened this issue May 19, 2018 · 0 comments

Comments

@csleary
Copy link

csleary commented May 19, 2018

Hi folks. I noticed the issue mentioned in the readme about using the latest version of SockJS in the browser and the resulting errors.

It looks like this has been raised in this thread, and can either be solved by making a tweak in the server middleware, or worked around by patching the connection function in the client to set the header opts.

I tried the latter monkeypatch when playing around with sockjs and webstomp-client (seems to be a more recent/active stomp client than sockjs), and found this sorted the issue for browser use. So perhaps including the earlier version of SockJS will no longer be necessary?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant