Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

How to turn off automatic https.

more options

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.

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.

Isisombululo esikhethiwe

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...

Funda le mpendulo ngokuhambisana nalesi sihloko 👍 1

All Replies (2)

more options

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).

more options

Isisombululo Esikhethiwe

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...