-
Notifications
You must be signed in to change notification settings - Fork 2.6k
"Don't upgrade connections to HTTPS (disabled)" is not working #30436
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
Comments
The above requires |
Verified
|
Brave | 1.52.115 Chromium: 114.0.5735.53 (Official Build) (x86_64) |
---|---|
Revision | c499d7ea22c8b2dba278465a5df7b86a8efa4e64-refs/branch-heads/5735@{#970} |
OS | macOS Version 11.7.7 (Build 20G1345) |
- Verified the STR from the description
- Reproduced the issue on
1.52.113
1.52.115 |
1.52.113 |
---|---|
![]() |
![]() |
Verification PASSED on
Using the STR/Cases outlined via #30436 (comment), ensured that http://https-everywhere.badssl.com is not being upgraded when
Verification PASSED on
Using the STR/Cases outlined via #30436 (comment), ensured that http://https-everywhere.badssl.com is not being upgraded when
|
Verification passed on
|
Description
"Don't upgrade connections to HTTPS (disabled)" is not working
Steps to reproduce
Don't upgrade connections to HTTPS (disabled)
http://https-everywhere.badssl.com/
> ObserveActual result
When
Don't upgrade connections to HTTPS (disabled)
setting is applied, pages are still opened and upgraded to HTTPS. The only way to disable forced upgrade to HTTPS is to turn off Shields. The same issue was observed on Nightly and Beta build, but not on Prod.timestamp_10-20-44_10-21-24.mp4
Expected result
No HTTPS upgrade must be triggered when
Don't upgrade connections to HTTPS (disabled)
setting is appliedIssue reproduces how often
Easily reproduced
Version/Channel Information:
Device details
Brave version
Brave build: 1.53.47
Chromium: 114.0.5735.26 (Official Build) canary (64-bit)
Revision: 7075cbb66f0542ac3e01ddfde6b813e7d61118a5-refs/branch-heads/5735@{#454}
Website problems only
Additional information
The text was updated successfully, but these errors were encountered: