Description of the issue:
I cannot run localhost for dev as it always gets upgraded to HTTPS. It only works in incognito, where the upgrade is not forced, however, that really isn’t a good experience.
Related Brave settings:
brave://settings/security → Always use secure connections: off
brave://flags → Use HTTPS by Default: Disabled
brave://flags → Allow invalid certificates for resources loaded from localhost: Enabled
Brave Version:
Version 1.61.116 Chromium: 120.0.6099.217 (Official Build) (64-bit)
Operating system information:
Edition: Windows 11 Home
Version: 23H2
Installed on: 10-Nov-23
OS build: 22631.3007
Experience: Windows Feature Experience Pack 1000.22681.1000.0
Oh, thanks for this information. Well, I cannot really find the option to turn it off and this did not work when typing http://localhost:2222 manually.
@JanSuran,
Yes I assumed that the advanced option would not work if it didn’t work after disabling Shields entirely — just wanted to show you where the option was/that you can expand that menu. Hope to have more information for you soon.
@Mattches any idea why theirs is different? Thought most or all Desktop would have same settings. Screenshot of my same window of Shields settings is below:
Actually I think the flag that you flipped is why it’s not appearing in default shields settings. So go back to brave://flags and change the #https-by-default flat to Enabled and the option will appear in Settings --> Shields again.
Attempt again to go to localhost and when you see the error message, go ahead and click the “tune” icon ()) in the address bar, then click where it says Connection is secure (or Insecure), then View certificate and share as screenshot of the resulting window?
Can you also please go to brave://net-internals/#hsts and, in the Query HSTS/PKP domain section, type in localhost and click Query and tell me what appears when it’s run?
@JanSuran,
On that same page (brave://net-internals/#hsts), in the Delete domain security policies, enter localhost in the Domain field and click Delete. Relaunch the browser and test again and let me know if this resolves the issue.