-
Notifications
You must be signed in to change notification settings - Fork 887
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
HTTPS by default for Desktop #16521
HTTPS by default for Desktop #16521
Conversation
|
A Storybook has been deployed to preview UI for the latest push |
A Storybook has been deployed to preview UI for the latest push |
components/brave_component_updater/browser/https_upgrade_exceptions_service.h
Outdated
Show resolved
Hide resolved
components/brave_component_updater/browser/https_upgrade_exceptions_service.cc
Outdated
Show resolved
Hide resolved
components/brave_component_updater/browser/https_upgrade_exceptions_service.h
Outdated
Show resolved
Hide resolved
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.
looks like most of comments are resolved, but I don't actually see the changes in PR. did you forget to push? 🤔
@goodov wrote:
Sorry for the confusion -- I haven't pushed yet because I'm working on the remaining comments. Will push when they are ready. |
d03b6b3
to
e7da857
Compare
A Storybook has been deployed to preview UI for the latest push |
A Storybook has been deployed to preview UI for the latest push |
The story so far: I pushed fixes for @goodov's comments in d03b6b3. But the PR had bitrotted so much that I then rebased it, and squashed those changes. In addition, I decided to remove to the Android UI code for now, to simplify this PR (e7da857). The browsertest is working in Android, except that there is a problem for all such web-page tests that needs to be fixed in brave/brave-browser#27837, so I have disabled the test in Android for now (4f98503). As of now all checks are green and ready to merge pending approval from reviewers. So the plan is to merge this Desktop-only PR first, and then get code/tests for Android working in a future PR. |
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.
++ android tests side. Please create a separate issue for Android as you mentioned and post it in that PR, so it's linked.
Thanks -- here's the Android issue: brave/brave-browser#28295. |
components/https_upgrade_exceptions/browser/https_upgrade_exceptions_service.cc
Outdated
Show resolved
Hide resolved
components/https_upgrade_exceptions/browser/https_upgrade_exceptions_service.cc
Outdated
Show resolved
Hide resolved
|
||
void SetUpOnMainThread() override { | ||
g_brave_browser_process->https_upgrade_exceptions_service() | ||
->SetIsReadyForTesting(); |
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.
I would also like to see a test that uses data from this service.
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.
That is a good idea. @goodov, if it's all right with you, I'd like to write that test in a follow-up PR (soon). In the meantime @pes10k and I are hoping to merge this PR into Nightly as soon as possible. (Hoping this is OK as the feature is disabled by default and we will roll out gradually.)
I opened an issue: brave/brave-browser#28330
A Storybook has been deployed to preview UI for the latest push |
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.
This looks really good to me. Well done @arthuredelstein !
The only big thing that needs to be checked before merging (maybe something we could easily add a test for?) is to ensure that HSTS sites never get downgraded since that would a major security issue.
chromium_src/chrome/browser/ssl/https_only_mode_navigation_throttle.cc
Outdated
Show resolved
Hide resolved
chromium_src/chrome/browser/ssl/https_only_mode_navigation_throttle.cc
Outdated
Show resolved
Hide resolved
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.
lgtm with few comments
chromium_src/chrome/browser/ssl/https_only_mode_navigation_throttle.cc
Outdated
Show resolved
Hide resolved
A Storybook has been deployed to preview UI for the latest push |
A Storybook has been deployed to preview UI for the latest push |
A Storybook has been deployed to preview UI for the latest push |
- Disabled, Standard, Strict modes - Controlled by global and per-site shields settings - Merge UI with HTTPS-Only Mode - Behind HttpsByDefault feature flag - Browser tests for each setting
18a4ccf
to
47e3c88
Compare
A Storybook has been deployed to preview UI for the latest push |
@@ -200,6 +202,10 @@ void BraveBrowserProcessImpl::StartBraveServices() { | |||
https_everywhere_service()->Start(); | |||
resource_component(); | |||
|
|||
if (base::FeatureList::IsEnabled(net::features::kBraveHttpsByDefault)) { |
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.
this is definitely not the right place for this check. All this is doing is delaying the initialization if the feature is disabled. The check should go inside HttpsUpgradeExceptionsService
For Desktop and Android:
Resolves brave/brave-browser#27141
Submitter Checklist:
QA/Yes
orQA/No
;release-notes/include
orrelease-notes/exclude
;OS/...
) to the associated issuenpm run test -- brave_browser_tests
,npm run test -- brave_unit_tests
wikinpm run lint
,npm run presubmit
wiki,npm run gn_check
,npm run tslint
git rebase master
(if needed)Reviewer Checklist:
gn
After-merge Checklist:
changes has landed on
Test Plan: