Fox News website not loading properly
I am located in Alabama and use a Mac desktop. I'm using Mozilla as my default browser 54.0.1 (64-bit). For years, I've had my web browser set with the following URL: www.foxnews.com Just recently within the last two to three weeks, I getting the following message (with a yellow caution exclamation mark) up in the left hand corner where I type in the URL stating the following:
www.foxnews.com Connection is not secure
Parts of this page are not secure (such as images)
Why am I getting this message? How can/ Is this being resolved? How can I resolve this issue without degrading my security configuration for my browser?
All Replies (11)
That sounds like a message about "mixed content" and more specifically being on a page with an HTTPS address which has some embedded images pulled from an HTTP address.
Fox News uses an HTTP connection by default. Perhaps you have installed HTTPS Everywhere or another add-on that upgrades your connection to an HTTPS connection? If a site is not designed for HTTPS, you may end up with a mixed content issue in that scenario.
If you are just reading news anonymously, this is not a concern. If you are entering sensitive or personal information, then I suggest asking the site to address the issue.
More info: Mixed content blocking in Firefox
jscher2000 ~
Thank you for the reply; however, when I switch the URL from https://www.foxnew.com to http://www.foxnew.com it automatically switches back to https://www.foxnew.com...
Where do I go/ What do I need to do to keep it from automatically switching back to https://www.foxnew.com ??
Some sites force HTTPS, like this one, and Google, but Fox News?? Seems unlikely.
Could it be an add-on like HTTPS Everywhere? You can view, disable, and often configure or remove extensions on the Add-ons page. Either:
- Command+Shift+a (Windows: Ctrl+Shift+a)
- "3-bar" menu button (or Tools menu) > Add-ons
In the left column, click Extensions. Then cast a critical eye over the list on the right side. Anything HTTPS or security related? As a test, you can disable any extensions you can live without for a couple of hours.
Often a link will appear above at least one disabled extension to restart Firefox before the change takes effect. You can complete your work on the tab and click one of the links as the last step.
Any difference?
Ok....
jscher2000,
This is what I just did... I went into the Firefox Preferences and deleted the cached web content. Set the Home Page to Mozilla Start Page... Now I'm getting the padlock with the red line across it...
RAllen said
Now I'm getting the padlock with the red line across it...
On which page? That icon may appear on an HTTP page with a login form, or an HTTPS page with a severe security problem.
I'm getting the padlock with the red line across it when I open http://www.foxnews.com
If I understand, I'm suppose to get this when opening http://www.foxnews.com because it's a combination of both secure and unsecured.... Correct?
I'm not seeing that icon, but then I have a lot of scripts blocked in the page. If you click it, is there a further explanation of the situation?
Nothing more than what I initially wrote in regards to the icon with the padlock with a red line drawn across it.
I bet if you unblock a lot of those scripts on http://www.foxnews.com/, you'll see the icon.
RAllen said
Nothing more than what I initially wrote in regards to the icon with the padlock with a red line drawn across it.
Originally you had a mixed display content icon and "Parts of this page are not secure (such as images)" but I don't think you said exactly what message is on the panel with the slashed lock.
I bet if you unblock a lot of those scripts on http://www.foxnews.com/, you'll see the icon.
No thanks.
The padlock with the red slash/ line is displayed in the left of the URL. If you click on the padlock with the slash/ line a dialogue box is displayed stating:
www.foxnews.com Connection is Not Secure
Logins entered on this page could be compromised.
Apparently Firefox is detecting a login form in the page (the second of the two articles I linked to here).
If you need to log into the site -- maybe to comment? -- it is better to change the address to an HTTPS address and accept the mixed display content warning than to submit your password with zero protection against interception.