Force HTTPS redirection for log in and sign up #319
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This implements client-side redirection to HTTPS of the
/signup
,/login
and/reset-password
views described in #139. If that view is mounted and is not on HTTPS then it's redirected, causing the app to reload.New projects are created with a
serveSecure: false
flag. After sign-up/log-in/reset, this flag is used to decide which protocol to redirect back to.serveSecure
defaults tofalse
. Until some user-facing UI switch is built (see #170) then it will always redirect back to HTTP.