-
Notifications
You must be signed in to change notification settings - Fork 274
is CORS working for anybody ? #204
Comments
Issue-Label Bot is automatically applying the label Links: app homepage, dashboard and code for this bot. |
@deresegetachew which browser are you using? chrome |
This is because there is no public superset instance for it to talk to. |
hi @williaster thank you for the response. I have tried both FireFox and Chrome ; I did set In chrome it fails to load the response data, while in fire-fox I get the token but still get a CORS Warning and also some error as shown below. I have attached a screen shot of the errors in chrome and firefox below. ---CORS Warning in FireFox and Error in Chrome-- Is there any reason why the flask app is not sending Acccess-Control-Allow-Origin Header ? Thank you in advance. |
hi @williaster any ideas how to solve this issues now i am working on moving to production ? |
Hello; The original code superset_config.py was missing a comma :( now it works.
|
* fix: Line not hidden after legend selection * fix: lint issues
The codebase on this repo has been moved to the main Apache Superset repo, and consequently the repo is in the process of being archived. See the Superset Improvement Proposal for details: apache/superset#13013 . While all currently open issues and PRs will be closed, we encourage you to reopen this issue on the main repo if it is still relevant. |
I have been trying to run superset-storybook for 2 days now and I keep on getting CORS error.
Yes I have followed the guides ; installed superset[cors] and set enable_cors to true;
other than that I have also followed this guide
#118 (comment)
looking at the response from the server i noticed we are not getting the response header
Access-Control-Allow-Origin
this is what my superset_config.py looks like
And the following are the error in chrome and HTTP request and response headers.
FYI the superset-storybook live demo does n't work as well.
https://apache-superset.github.io/superset-ui/
has any one faced the same issue ?
thank you
The text was updated successfully, but these errors were encountered: