[X] My Assistant

Open a new tab and type about:config in the location bar as the URL to go to. about: URLs are Firefox internal URLs.

Longer version: [kb.mozillazine.org] http://kb.mozillazine.org/About:config

thank you as well. i should of asked this a while ago but i was being stubborn and trying to see if i could do it on my own.

thank you as well. i should of asked this a while ago but i was being stubborn and trying to see if i could do it on my own.

Protip if you have a browser related problem put it into google. In this case I put in firefox about config and it was the first result. Thanks for helping me with my Firefox problems Google.

This post has been edited by ryuukami123: Jan 28 2017, 10:29

Check the ongoing discussion of HSTS prinning.

Thanks to you and to original poster, I think that actually helped.

thanks for the explaination hzqr, I disable it on the config, and now it even loads pages faster than it used to, I should have done this a long time ago

Thanks for giving me the solution, blue penguin, disabling hsts priming fixed everything!

Thank you very much for the help on getting this problem sorted out! As for those who may not look at the first page because of TLDR:

Go into about:config
Look up "security.mixed_content" without quotes

find the one that says "security.mixed_content.send.hsts.priming" without quotes

Set that one, and only that one, to false.
Don't change any of the other settings, because those are fine and have some importance that escapes me.

Hope this helps, and I take no credit for this fix, it was Blue Penguin's post on how to get this fix that helped me
(IMG:[invalid] style_emoticons/default/laugh.gif)

The tl;dr version is Firefox is slowly (but surely) becoming shit and getting dangerously close to Safari - and soon... Internet Explorer.

Firefox 51 is another catastrophe. Amending the wiki to let people know Firefox is shit, even the stable version, as it fails to respect PROTOCOL COMPLIANCE 101.

Before I disabled HSTS Priming, galleries were actually working better for me on IE than FF. And that's with the E-Hentai support team explicitly ignoring IE support, if not actively trying to break it.

This post has been edited by conundrum: Jan 29 2017, 08:51

Site is broken in Firefox 51.0.1 . I can't load any images even in safe mode (no ad-ons turned on).

This just plain doesn't load: https://e-hentai.org/g/1008110/c31f506589/

But it works perfectly fine in Chrome.

Site is broken in Firefox 51.0.1 .

Read the thread.

https://forums.e-hentai.org/index.php?s=&am...t&p=4749944

This post has been edited by CoLd As IcE: Jan 30 2017, 17:49

Site is broken in Firefox 51.0.1

Firefox 51.0.1 is broken.

Firefox 51.0.1 is broken.

not rly if u apply fix it loads images fast worked for me

not rly if u apply fix it loads images fast worked for me

It's broken unless you manually change a setting to fix it. Still broken by default.

disabling security.mixed_content.send_hsts_priming fixed it, thanks!

btw you could put up some sort of announcement directly on the galleries so everyone using firefox will know right away

This post has been edited by progste: Jan 30 2017, 19:17

It's broken unless you manually change a setting to fix it. Still broken by default.

then u say its broken but there is a fix dont mislead when u know there is a fix --.--

then u say its broken but there is a fix dont mislead when u know there is a fix --.--

If my car is broken but I know a guy who can fix it, I still say it is broken.

This Firefox version is broken, the fact that there is a fix that people have had to find for themselves doesn't change that.

If Firefox 51 wasn't broken, there wouldn't be [bugzilla.mozilla.org] an official bug entry flagged as an unresolved blocker for Firefox 51.

yeah but if the inside interior has a chip in it doesn't mean its broken (car analogy u had going) and need to go to the car dealer to get fixed it still works. ^^
any way you win ^^ its broken

This post has been edited by CoLd As IcE: Feb 1 2017, 04:48

This is an old topic, but I feel it's worth necroing to point out that as of now, at least on the ESR (currently version 52.1.0 ESR), security.mixed_content.send_hsts_priming now defaults to false. It appears they realised it was broken, and disabled it themselves. I would presume the mainstream release also does the same, but it breaks some of my addons, so I'd have to use someone else's computer to check.

So, this problem is either gone for good unless you explicitly enable priming, or may crop up again in the future if they enable priming again (which would force us to disable it again).

What addons are broken by that setting? Nothing should be using HSTS priming...