4 ms·

What happens if i need to access localhost on http?

jstsch 6y ago
From the article: Firefox asks for your permission before connecting to a website that doesn’t support secure connections.
fiskfiskfisk 6y ago
It's explained in the post: > For the small number of websites that don’t yet support HTTPS, Firefox will display an error message that explains the security risk and asks you whether or not you want to connect to the website using HTTP. Here’s what the error message looks like: ..
iso1631 6y ago
"Firefox asks for your permission before connecting to a website that doesn’t support secure connections." That suggests it will ask you for permission, presumably with a "always remember this choice" option.
pedrogpimenta 6y ago
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.
- agilob 6y ago
  It could be a bit smarter and detect if connection is to a local server.
- Doctor_Fegg 6y ago
  No need for snark. It's a legit question and buildfocus's answer below is relevant: "browsers generally treat localhost and/or 127.0.0.1 as secure origins in themselves anyway"
- StreamBright 6y ago
  I have read it, I was wondering about localhost explicitly.
DixieDev 6y ago
As described in the article HTTPS-Only mode is opt in, you can also disable it at will, you can add exceptions on a site-by-site basis, and even when it's on you are prompted on whether or not you wish to proceed to non-HTTPS sites.
- ugkjkvv 6y ago
  hvhfjfhjvf
everfree 6y ago
My guess is that either there's a built-in rule for that, or you can just click the "Continue to HTTP Site" button like in the screenshot.
alufers 6y ago
It will probably be a hardcoded exception, just like for enabling microphone/webcam access and other features today.
- alufers 6y ago
  To add to this: What interests me is how will they handle accessing the management interface of routers and various network equipment once HTTP gets deprecated.
buildfocus 6y ago
As other posters mention, you can disable this when you need to, but also browsers generally treat localhost and/or 127.0.0.1 as secure origins in themselves anyway, so I suspect that won't be necessary. See https://developer.mozilla.org/en-US/docs/Web/Security/Secure_Contexts#When_is_a_context_considered_secure https://developer.mozilla.org/en-US/docs/Web/Security/Secure...: > Locally-delivered resources such as those with http://127.0.0.1 http://127.0.0.1 URLs, http://localhost http://localhost and http://*.localhost http://*.localhost URLs (e.g. http://dev.whatever.localhost/ http://dev.whatever.localhost/), and file:// URLs are also considered to have been delivered securely.
xaldir 6y ago
It would help greatly if this kind of things (that and security exceptions would not apply to any host in the RFC1918 address space. Would make life easier for IT dept around the world.
SummerlyMars 6y ago
Just tried it after enabling the feature - No message, accessing localhost works just fine over http.

From the article: Firefox asks for your permission before connecting to a website that doesn’t support secure connections.

fiskfiskfisk 6y ago

It's explained in the post: > For the small number of websites that don’t yet support HTTPS, Firefox will display an error message that explains the security risk and asks you whether or not you want to connect to the website using HTTP. Here’s what the error message looks like: ..

iso1631 6y ago

"Firefox asks for your permission before connecting to a website that doesn’t support secure connections." That suggests it will ask you for permission, presumably with a "always remember this choice" option.

pedrogpimenta 6y ago

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.

agilob 6y ago
It could be a bit smarter and detect if connection is to a local server.
Doctor_Fegg 6y ago
No need for snark. It's a legit question and buildfocus's answer below is relevant: "browsers generally treat localhost and/or 127.0.0.1 as secure origins in themselves anyway"
StreamBright 6y ago
I have read it, I was wondering about localhost explicitly.

DixieDev 6y ago

As described in the article HTTPS-Only mode is opt in, you can also disable it at will, you can add exceptions on a site-by-site basis, and even when it's on you are prompted on whether or not you wish to proceed to non-HTTPS sites.

ugkjkvv 6y ago
hvhfjfhjvf

everfree 6y ago

My guess is that either there's a built-in rule for that, or you can just click the "Continue to HTTP Site" button like in the screenshot.

alufers 6y ago

It will probably be a hardcoded exception, just like for enabling microphone/webcam access and other features today.

alufers 6y ago
To add to this: What interests me is how will they handle accessing the management interface of routers and various network equipment once HTTP gets deprecated.

buildfocus 6y ago

As other posters mention, you can disable this when you need to, but also browsers generally treat localhost and/or 127.0.0.1 as secure origins in themselves anyway, so I suspect that won't be necessary. See https://developer.mozilla.org/en-US/docs/Web/Security/Secure_Contexts#When_is_a_context_considered_secure https://developer.mozilla.org/en-US/docs/Web/Security/Secure...: > Locally-delivered resources such as those with http://127.0.0.1 http://127.0.0.1 URLs, http://localhost http://localhost and http://*.localhost http://*.localhost URLs (e.g. http://dev.whatever.localhost/ http://dev.whatever.localhost/), and file:// URLs are also considered to have been delivered securely.

xaldir 6y ago

It would help greatly if this kind of things (that and security exceptions would not apply to any host in the RFC1918 address space. Would make life easier for IT dept around the world.

SummerlyMars 6y ago

Just tried it after enabling the feature - No message, accessing localhost works just fine over http.