Closed 1270011 closed 1 year ago
https://brave.com/privacy-updates/22-https-by-default/
It starts in v1.50 .. current test (issue 51) is using Brave 1.49
Thanks for keeping an eye on this @1270011! Indeed @Thorin-Oakenpants is right that Brave is currently rolling out the HTTPS by Default feature in 1.50. You can see all but the "insecure website" test passes in Brave Nightly 1.51: https://privacytests.org/nightly.html
... aaaaaaaand ... issue 52 shows it failed (desktop says 1.50, shows upgradable address/hyperlinks as X) - did the feaure miss the boat?
@Thorin-Oakenpants -- no, it's rolling out gradually. Currently at 15% of clients.
@Thorin-Oakenpants -- no, it's rolling out gradually. Currently at 15% of clients.
Is there a resource where you can find the progress status?
@Thorin-Oakenpants -- no, it's rolling out gradually. Currently at 15% of clients.
Is there a resource where you can find the progress status?
You can follow this file: https://github.com/brave/brave-variations/blob/production/seed/seed.json#L1889. It currently indicates that the HttpsByDefault feature is at 15% in Release for Desktop and Android.
The features of HTTPS in the browser testing section in brave are apparently not correct. Brave supports https on all sites, which is realized through the integrated Brave shields. This integration is based on https everywhere. Here are the related links:
However, it is possible that the user have to manually activate the feature. If you like, I could test it if it is enabled by default or not after a clean install of brave. The correspondig setting can be found in:
brave://settings/security
I would be very pleased about feedback and the further procedure. Thank you!