How to turn off automatic https.
When I visit an http site and specify a non-standard port, it automatically changes to https, which is not a site redirect but something Firefox changes. This site already has an https service, and the http service will redirect to https. I reproduced the same situation in chrome. Accessing the http service with a non-standard interface was normal. After accessing the https service once, the service with the non-standard port was also changed to https. Clearing the data will restore it. Is this cached? My HTTPS-Only Mode is turned off, and set an exception for this site. thx.
Wybrane rozwiązanie
szerr said
I reproduced the same situation in chrome. Accessing the http service with a non-standard interface was normal. After accessing the https service once, the service with the non-standard port was also changed to https. Clearing the data will restore it. Is this cached?
Sites can send browsers a Strict Transport Security header instructing the browser to always use HTTPS. See:
https://developer.mozilla.org/docs/Web/HTTP/Headers/Strict-Transport-Security
Browsers sometimes differ on the scope of the instruction, but in this case, it sounds like both Firefox and Chrome are in agreement that it covers all ports for that host.
Firefox stores HSTS instructions in a text file in your profile, and probably if you delete data for a specific site, it will clear that instruction, too. But of course, it will be saved again the next time...
Przeczytaj tę odpowiedź w całym kontekście 👍 1Wszystkie odpowiedzi (2)
Does it still happen if you go to about:config and change network.dns.upgrade_with_https_rr to false?
Private windows will try HTTPS first (dom.security.https_first_pbm).
Wybrane rozwiązanie
szerr said
I reproduced the same situation in chrome. Accessing the http service with a non-standard interface was normal. After accessing the https service once, the service with the non-standard port was also changed to https. Clearing the data will restore it. Is this cached?
Sites can send browsers a Strict Transport Security header instructing the browser to always use HTTPS. See:
https://developer.mozilla.org/docs/Web/HTTP/Headers/Strict-Transport-Security
Browsers sometimes differ on the scope of the instruction, but in this case, it sounds like both Firefox and Chrome are in agreement that it covers all ports for that host.
Firefox stores HSTS instructions in a text file in your profile, and probably if you delete data for a specific site, it will clear that instruction, too. But of course, it will be saved again the next time...