We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
New branding option like enforce_secure_connection (boolean):
enforce_secure_connection
true
false
In case http is not allowed and URL under http is typed, a correct error will be shown like non-secured traffic not allowed
non-secured traffic not allowed
Only checked in login view, not dynamic (at least in first iteration)
Default value: false (traffic allowed in vanilla app)
Reference: https://github.com/owncloud/enterprise/issues/5769
The text was updated successfully, but these errors were encountered:
New branding option like prevent_http (boolean):
prevent_http
Better name enforce_https or enforce_ssl?
enforce_https
enforce_ssl
Sorry, something went wrong.
yes, sounds more positive
Let's call it enforce_secure_connection
manuelplazaspalacio
Successfully merging a pull request may close this issue.
New branding option like
enforce_secure_connection
(boolean):true
: http traffic not allowed, just httpsfalse
: http traffic allowedIn case http is not allowed and URL under http is typed, a correct error will be shown like
non-secured traffic not allowed
Only checked in login view, not dynamic (at least in first iteration)
Default value:
false
(traffic allowed in vanilla app)Reference: https://github.com/owncloud/enterprise/issues/5769
TASKS
PR
The text was updated successfully, but these errors were encountered: