This has started happening a while ago (previously there was not perceptible delay) and luckily I don’t have to visit HTTP sites very often but it is annoying and I would like to get rid of it.
I know HTTP is bad TYVM. I only use this HTTPS-only mode to forcibly upgrade to HTTPS whenever possible and be notified if it doesn’t work.
Does anyone know why this is happening and how to disable it?
#Firefox @firefox@lemmy.world
I have not seen that unless it’s some sort of new feature, but if so, that will get quite annoying, quite fast as I access my server locally via HTTP with the IP address.
You can add exclusions
Pressing “Continue to HTTP Site” actually adds it to the allow-lists already which is quite handy (if it weren’t for the annoying delay now…)
And can I turn this off?
I wonder if there’s a way to do that on mobile.
Does security.dialog_enable_delay work on that?
It does not. It’s also 5s, not 1s, so that couldn’t have been it.
Btw, Googling that option, I found out that there’s a reason for this delay and it’s security: https://www.squarefree.com/2004/07/01/race-conditions-in-security-dialogs/
That timeout should indeed only last the value of
security.dialog_enable_delay, so 1s. If it is 5s for you, it would be nice if you write a bug report, maybe with a screen recording.Huh, after a restart it appears to honour that setting; it’s now 1s and that’s an acceptable security trade-off.
I’m not 100% sure but there may have been an update that was applied by the restart.
I don’t believe you can get rid of that screen, or the newly added delay, if you have firefox set to HTTPS Only mode
Looking at the support site, the only exceptions that seem to exist there are on a per-site basis: https://support.mozilla.org/en-US/kb/https-only-prefs
You could try poking around in the about:config I guess just in case it hasn’t been documented yet.
Edit: added link and extra info
Note that I only want to get rid of the delay before being allowed to press the button, not the screen itself. I want an HTTP connection to remain an action I must explicitly initiate (as it should be).
I also noticed that and I assume it’s because they want people to actually read the warning and not just click continue without thinking.
