-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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 Android #28295
Comments
See QA testing info here: brave/brave-core#17581 (comment) |
QA can also use brave/brave-variations#560 (comment) as a template. Those are the cases that I went through verifying the feature before enabling it via Griffin 👍 CCing @Uni-verse @stephendonner |
Verification Completed on
Case: Griffin ExperimentVariations server URL: https://variations.bravesoftware.com/seed
Case: brave://flags
Case: New Profile (Negative Test Case)
Case: Require all connections to use HTTPS (strict)
Case: Upgrade to HTTPS whenever possible (default)
Case: Don't upgrade connections to HTTPS (disabled)
Case: Globals
Case: Per-site settings
Case: Shields Toggle
Case: Private Browsing
Case: Upgraded Profile
Testing upgrading from 1.50.99 -> 1.51.85 covered in #28295 (comment)
Changing preference post-upgrade (http.badssl.com)
|
Verification Completed on
Case: Griffin ExperimentVariations server URL: https://variations.bravesoftware.com/seed
Case: brave://flags
Case: New Profile (Negative Test Case)
Case: Require all connections to use HTTPS (strict)
Case: Upgrade to HTTPS whenever possible (Default)
Case: Don't upgrade connections to HTTPS (disabled)
Case: Globals
Case: Per-site settings
Case: Shields Toggle
Case: Private Browsing
Case: Upgraded Profile
Defaults (Not changing HTTPS globals, 1.50.99 -> 1.51.79)
Strict (Always use secure connection enabled, 1.50.99 -> 1.51.79)
Disabled (Disable HTTPS in global settings, 1.50.99 -> 1.51.79)
|
Verification Completed on
Fresh Profile
Upgraded Profile
|
Once we have resolved #27141, we plan to add a UI for HTTPS by Default on Android.
The text was updated successfully, but these errors were encountered: