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

Duplicate values in CORS header when using socket.io #4025

Closed
ricwo opened this issue Jul 16, 2019 · 4 comments
Closed

Duplicate values in CORS header when using socket.io #4025

ricwo opened this issue Jul 16, 2019 · 4 comments
Labels
area:rasa-oss 🎡 Anything related to the open source Rasa framework type:bug 🐛 Inconsistencies or issues which will cause an issue or problem for users or implementors.

Comments

@ricwo
Copy link
Contributor

ricwo commented Jul 16, 2019

Rasa version: 1.1.6

Python version: 3.6

Operating system (windows, osx, ...): osx

Issue:

Error (including full traceback):

Access to XMLHttpRequest from origin has been blocked by CORS policy: The ‘Access-Control-Allow-Origin’ header contains multiple values, but only one is allowed.
@ricwo ricwo added the type:bug 🐛 Inconsistencies or issues which will cause an issue or problem for users or implementors. label Jul 16, 2019
@wochinge wochinge added the area:rasa-oss 🎡 Anything related to the open source Rasa framework label Jul 24, 2019
@wochinge
Copy link
Contributor

@akelad

@akelad
Copy link
Contributor

akelad commented Aug 22, 2019

@wochinge it's fixed with the PR now right?

@wochinge
Copy link
Contributor

Yes!

This was referenced Aug 22, 2019
@tmbo
Copy link
Member

tmbo commented Sep 4, 2019

I will close this as it should be fixed now.

@tmbo tmbo closed this as completed Sep 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:rasa-oss 🎡 Anything related to the open source Rasa framework type:bug 🐛 Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants