Hi miggz, I heard somewhere else that there can occasionally be conflicts between this feature of HTTPS Everywhere and ad blocking extensions like uBlock Origin. It points to a more general issue.

Firefox provides a way for add-ons to intercept and modify responses from websites. If more than one extension is using the same method of monitoring and modification, only one of them can succeed, and the order -- or "winner" -- is not predictable and consistent. So that could explain why sometimes you need to reload, which lets both extensions try again and maybe the winner changes.

Or maybe it's something else. Intermittent problems are hard to diagnose.

jscher2000 said

Hi miggz, I heard somewhere else that there can occasionally be conflicts between this feature of HTTPS Everywhere and ad blocking extensions like uBlock Origin. It points to a more general issue. Firefox provides a way for add-ons to intercept and modify responses from websites. If more than one extension is using the same method of monitoring and modification, only one of them can succeed, and the order -- or "winner" -- is not predictable and consistent. So that could explain why sometimes you need to reload, which lets both extensions try again and maybe the winner changes. Or maybe it's something else. Intermittent problems are hard to diagnose.

How do you explain this friends? Happens every time I try to give feedback. HTTPS everywhere is on to block all non-HTTPS connections mode.

miggz said

How do you explain this friends? Happens every time I try to give feedback. HTTPS everywhere is on to block all non-HTTPS connections mode.

This will prolly take a long time for an answer, I can wait.

Hi miggz, when you click Google's own feedback link, it introduces insecure content into YouTube?

That's hard to explain, since it's their own site. Also, that doesn't happen on mine (screenshot attached; I block Doubleclick, in case that is relevant).

Could it be related to a user style or extension modifying the page on your Firefox?

This is a long thread, so I'm not sure whether it might already have been mentioned: sometimes when Firefox uses content from cache, it is considered insecure even if it was originally retrieved using HTTPS. To rule out that issue, you could reload the page bypassing the cache, for example using Ctrl+Shift+r.

jscher2000 said

Hi miggz, when you click Google's own feedback link, it introduces insecure content into YouTube? That's hard to explain, since it's their own site. Also, that doesn't happen on mine (screenshot attached; I block Doubleclick, in case that is relevant). Could it be related to a user style or extension modifying the page on your Firefox?

---

This is a long thread, so I'm not sure whether it might already have been mentioned: sometimes when Firefox uses content from cache, it is considered insecure even if it was originally retrieved using HTTPS. To rule out that issue, you could reload the page bypassing the cache, for example using Ctrl+Shift+r.

Thanks so much! I love you man! I do have stylish add-on installed. Any way i can put Https everywhere at top priority for all browser network exchange? I lose my cool real fast and it is hard for me to explain things, sorry I am trying my best and many thanks! I love you nightly FF

miggz said

I do have stylish add-on installed.

Maybe that user style is injecting something insecure? I don't know whether one extension can police another's request.

Ok, thanks man. If you ever find more info please post it here and Mods please leave this thread unlocked till it is fully solved with all info that I gave. I just want an "only https conection" no matter what and popups for non-https requests from browser. should I take this to HTTPS everywhere add-on for help? I am sure firefox guru(they are gods) has a fix or can make one, Why not just make the option in settings and say FU fix your site or what ever is the culprit?

Like sign an add-on to be a top priority add-on that can/will re-route/disable or take control of other add-ons and manage everything that would conflict or cause the add-on to break. This is my last post till others add more info. (please no more add-ons, just make FF better.)

Threads lock when they turn 6 months old, so we have about a week left on this one.

Did you already experiment with the built-in settings to have Firefox try to upgrade insecure images from HTTP to HTTPS, or to completely block HTTP images in HTTPS pages?

https://www.jeffersonscher.com/res/mixed-display.html

jscher2000 said

Threads lock when they turn 6 months old, so we have about a week left on this one. Did you already experiment with the built-in settings to have Firefox try to upgrade insecure images from HTTP to HTTPS, or to completely block HTTP images in HTTPS pages? https://www.jeffersonscher.com/res/mixed-display.html

Thanks for link and info. Will try later, all tapped out on the will to mess with settings right now.