Has anyone else installed Firefox v92 and then had this strange and VERY irritating occurrence as did I last evening with FF v92 on Debian 11 ?

All of a sudden it was locked-in at 'https only' and would not allow access
any sites that were strictly on http and not https .

Checked the settings and it was set for "Don't enable https-only mode".

If that's how it's gonna be with FF v92.... than I'll be staying with older versions.

Just in case Slackware goes to v92 and the same thing happens...
have already saved a copy of the v91.1.0esr package to revert back to.

-rw-r--r-- 1 root root 56625768 Sep 6 13:07 /archives/saved_packages/mozilla-firefox-91.1.0esr-x86_64-1.txz

Unfortunately, those HTTP only sites are doomed. That's it.

And the switching to 91 ESR release as Slackware did, will only delay their doom with no more than ONE year.

The bad thing is that the next major ESR release, published after around ONE year in future, I guess will have no HTTP support at all - probably there will not be even a switch to enable them.

This ONE year of HTTP support is not so much. After all, this means roughly 20% of the time required to develop Slackware 15.0 and considering that a Slackware release has a support around 8 years, this ONE year represents roughly 12% of support time.

That's WHY I wonder if is really worth for Slackware 15.0 to claim that has HTTP support on its Firefox...

@glennmcc -- I have not tried v92.0 in anything other than https only mode, so cannot say.
The option to proceed to the insecure site does exist, so why doesadded security irritate so much, I wonder?

Go Ducks!

Enable/Disable HTTPS-Only Mode

https://support.mozilla.org/en-US/kb...ttps-only-mode

lonestar_italy,

Thanks for the link but as stated in the original post....
it's already disabled but is still preventing access to http-only sites
by changing http in the URL's protocol to https which that site does not use.

try also disable the browser.urlbar.autofill in about:config

autofill also already disabled

All known options to keep it from happening have now been tried and still
manually entering http://glennmcc.org/ results in the URL being changed to https:///glennmcc.org/
the moment the Enter key is pressed.

Also, clicking a link to http://glennmcc.org/ or any other http URL
results in the URL being changed to https just as-if the setting were to always use https

The problem _seems_ to be that FF92 is ignoring the "Don't enable https-only mode" setting.

This can occur also if the server is set up this way, as is mine. Using any browser http://slint.fr will redirect to https://slint because I don't want any http connection to my server.

1 members found this post helpful.

Such is not the case.

http://glennmcc.org/ is strictly HTTP... no HTTPS access available at-all.

The same for my own server running here at home on Slackware64-current

http://glennmcc.dynu.com/

This is perfectly fine. Just be aware that this will prevent more and more people to visit these websites, be it with firefox or other web browsers.

http://glennmcc.dynu.com/my-stuff/videos/never_mind.web

I guess it was needless for me to post that link.
You won't be able to get it 'cus you have 'https-only' enabled.

;-)

This is not actually expected behaviour of Firefox 92, the setting for https-only mode still works. I'm not sure what's screwy about the package or environment you are using in your debian distro. I can go to your web site just fine.

I absolutely detest forced https where https is not necessary, so I'd know right away. If I type http:// to go to a site, it better damned well use http. My sites are http too, though lately I've given in and use certificates so https will also work.

I do my own Firefox builds, but consider unpacking binaries from mozilla.org to test it. You can unpack the archive and run it in place.

https://ftp.mozilla.org/pub/firefox/...x-92.0.tar.bz2

I'd probably start it like

And start it with a new profile so it doesn't mess with your old one.

I tried HTTPS-Only Mode, but it wasn't as good yet as "Don’t enable HTTPS-Only Mode" with HTTPS Everywhere.

Really? How long does that take?

Well, actually, this matter of https is somewhat problematic and a threat to the free web. Not everyone can and/or will or even need https on their website, and in some cases it serves no purpose at all. Blocking or warning against http just threatens to split the web. And this promotion of https only is a threat to hobbyists and people with less resources and others as well.

I like https only where it serves a purpose. But http also serves a purpose, and not everything needs to be https. It seems to be more of an unreasonable hysteria at this point, feeding on people who don't understand web technology.

1 members found this post helpful.