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

Feature: Updated more fine grained support for CORS in QueryResultAPI #483

Merged
merged 2 commits into from
Jul 13, 2015
Merged

Conversation

erans
Copy link
Contributor

@erans erans commented Jul 13, 2015

No description provided.

@landscape-bot
Copy link

Code Health
Repository health decreased by 0.23% when pulling 1a36575 on erans:master into 666e328 on EverythingMe:master.

@landscape-bot
Copy link

Code Health
Code quality remained the same when pulling 4a7c066 on erans:master into 666e328 on EverythingMe:master.

# In most cases all you need to do is set REDASH_CORS_ACCESS_CONTROL_ALLOW_ORIGIN
# to the calling domain (or domains in a comma separated list).
ACCESS_CONTROL_ALLOW_ORIGIN = set_from_string(os.environ.get("REDASH_CORS_ACCESS_CONTROL_ALLOW_ORIGIN", ""))
ACCESS_CONTROL_ALLOW_CREDENTIALS = parse_boolean(os.environ.get("REDASH_CORS_ACCESS_CONTROL_ALLOW_CREDENTIALS", "false"))
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why parse_boolean here and convert to string above? just keep it string.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because I need to verify its a valid value. I prefer to do it while we read the configuration and not when I'm setting it

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

Successfully merging this pull request may close these issues.

3 participants