Skip to content

Omit "Accessing site insecurely via HTTP." warning if HTTP is secure enough #37330

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.

Sign up for GitHub

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

Merged
szaimen merged 2 commits into from
Apr 18, 2023
Merged

Omit "Accessing site insecurely via HTTP." warning if HTTP is secure enough #37330

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e3f1fae
Omit "Accessing site insecurely via HTTP." warning if HTTP is secure …
Al2Klimov Mar 21, 2023
ff02b07
Drop broken unit test
Al2Klimov Mar 25, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
Omit "Accessing site insecurely via HTTP." warning if HTTP is secure … 
…enough

This is the case for localhost and Tor hidden services.

Signed-off-by: Alexander A. Klimov <[email protected]>
  • Loading branch information
@Al2Klimov @szaimen
Al2Klimov authored and szaimen committed Apr 17, 2023
commit e3f1fae715e7787e516df4a8aa6fcedf6c0e531d
2 changes: 1 addition & 1 deletion core/js/setupchecks.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -717,7 +717,7 @@
type: OC.SetupChecks.MESSAGE_TYPE_WARNING
});
}
} else {
} else if (!/(?:^(?:localhost|127\.0\.0\.1|::1)|\.onion)$/.exec(window.location.hostname)) {
messages.push({
msg: t('core', 'Accessing site insecurely via HTTP. You are strongly advised to set up your server to require HTTPS instead, as described in the {linkstart}security tips ↗{linkend}.')
.replace('{linkstart}', '<a target="_blank" rel="noreferrer noopener" class="external" href="' + tipsUrl + '">')
Expand Down