Hardcode https redirects #1114
Closed
Hardcode https redirects #1114
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Other https settings are already selected (redirecting 80 to 443) so why not harcode the redirects too? The existing $scheme breaks "System Overview" checks if nextcloud is placed behind an ssl terminating proxy, as it'll return http links which see a further redirect. Who doesn't enable https?
|
/backport to master |
|
See the discussion in #899 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Other https settings are already selected (redirecting 80 to 443) so why not hardcode the redirects too?
The existing $scheme breaks "System Overview" checks if nextcloud is placed behind an ssl terminating proxy, as it'll return http links which see a further redirect.
Who doesn't enable https?