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
Add force_ssl flag to Riak Control. #164
Conversation
Separate out authentication type and forced SSL requirements. Specifically, a user should be able to force SSL when using no authentication, or force non-SSL when using authentication given they may already be on a protected network.
Discussed this in HipChat, but a third option would be to default to the old way when this setting was |
I just pushed an updated commit, 85378b7, which I believe addresses the upgrade concern correctly. |
Addressed by #164. |
Rather, addresses #156. |
_ -> | ||
case wrq:scheme(RD) of | ||
https -> | ||
case app_helper:get_env(riak_control, force_ssl, undefined) of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
undefined
is the default.
This looks good at first glance, I'll give it a test tomorrow. |
Did you get a chance to test this? |
|
All possible combinations check out as expected. 👍 to merge |
Perfect; thanks. |
Add force_ssl flag to Riak Control.
basho/riak_test#412 covers a majority of the cases here, but is not exhaustive. |
Separate out authentication type and forced SSL requirements.
Specifically, a user should be able to force SSL when using no
authentication, or force non-SSL when using authentication given they
may already be on a protected network.
@seancribbs @joedevivo