-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
cors_origins is empty #1880
Comments
I tried passing the cors option as the command argument and it worked fine.
|
Yes, so the configuration within the |
taytzehao
pushed a commit
to taytzehao/rasa
that referenced
this issue
Jul 14, 2023
…aHQ#1880) Bumps [github.com/moby/buildkit](https://github.com/moby/buildkit) from 0.11.5 to 0.11.6. - [Release notes](https://github.com/moby/buildkit/releases) - [Commits](moby/buildkit@v0.11.5...v0.11.6) --- updated-dependencies: - dependency-name: github.com/moby/buildkit dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Rasa Core version: 0.7.9
Python version: 3.6
Operating system (windows, osx, ...): OSX
Issue:
came across CORS issue while trying to run the rasa_core.server.
Then changed the config file to include the cors_origins
Here is how my config.json looks like
Tried to debug the code under rasa_nlu (server.py) and found that the configuration is empty
logs:
Therefore response to my request was always 403.
Kindly let me know if I am missing anything. Thank you in advance!
The text was updated successfully, but these errors were encountered: