31–40 of 525 posts
What happens if i need to access localhost on http?
You could start by reading the article, even only the first paragraph: > Firefox asks for your permission before connecting to a website that doesn’t support secure connections.
"browsers generally treat localhost and/or 127.0.0.1 as secure origins in themselves anyway"
Earlier quoted context omitted.
Your post is brief, and has a grammar error that makes it harder to understand.
the second "still" is meant to be "sell" or "make".
What happens if i need to access localhost on http?
You could start by reading the article, even only the first paragraph: > Firefox asks for your permission before connecting to a website that doesn’t support secure connections.
What particularly annoyed me was using http to sites which supported https.
As a developer I likely won't use this feature much, considering most of our internal development sites are http only. For the general public it might be useful though, especially the auto-upgrade feature, protecting them from the lazy network operators that didn't add a proper auto-redirect.
I’m surprised at the negative knee-jerk reaction. I actually love this idea immediately. It encapsulates something I kind of already wanted when using HTTPS Everywhere. This doesn’t guarantee the transport is end-to-end secure; I’m sure plenty will strip the encryption at an LB and then possibly send it back over the internet. But, I think it’s a good addition nevertheless. Here’s to hoping for more DoH and encrypted…
HTTPS upgrade feature has always been there in Brave.
Edit: I'm using system-wide DoT at the moment with CoreDNS but it doesn't work that well. Not sure why.
One change I'd like to see in browsers is when the user enters a domain without protocol in the url bar it interprets that as https instead of http.
However, I'm not sure whether it'd be best to make this the mode the default for everyone. I imagine regular users would be quite scared/confused when encountering such a message, and that might lead to lots of valuable (mostly older) websites still running plain HTTP to be effectively cut off.
I wonder how it will work against websites like http://neverssl.com (which helps me to log in to some wifi portals, HTTPS Everywhere shows the prompt for a temporary exception.)