Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Google is not secure via Https

  • 28 பதிலளிப்புகள்
  • 1 இந்த பிரச்சனை உள்ளது
  • 113 views
  • Last reply by jscher2000

I have an issue with google.com using https on Firefox 61.01 running on Mac OS High sierra. July-9-2018

When I went to "https://www.google.com" while in private mode and with multiple tabs opened I received a message that it is not secure. this is a problem with Firefox because I opened a new Firefox window and then went to "https://www.google.com" and It opened as secure. See my enclosed sceen shot.

-Note just as I was posting this message firefox crashed and I had to retype the message. -Crash ID 31cbf8d6-7f5a-4a0c-b709-2278e1180709 has been submitted.

Attached screenshots

Mace2 மூலமாக திருத்தப்பட்டது

All Replies (8)

Cor-el I do not see "forget about this site" keep i mind I am using a Mac OS.

Also this issue is not mixed insecure content. I opened another tab within firefox and it showed the https in the url bar. this suggests that Firefox is occasionally getting tripped up and shows a https as http non secure. this occurred while watching yoututbe and allowing it to automatically play the next youtube video.

I have not received a response from Cor-el regarding his suggestion.

This is what I see in my right hand corner context menu. see enclosed

You only see "Forget About This Site" in the right-click context menu of a history item. That should work in the history sidebar and in the History Manager (Library). The screenshot shows the "3-bar" Firefox menu button drop-down list.

Cor-el That option "clear recent history" is greyed out on all sites I go to which I believe is due to me operating in private browsing mode.

Another example has occurred.

The URL is https://www.google.com/search?biw=1280&bih=613&tbm=isch&sa=1&ei=pnWFW_b6EZHWsAHkkoXoDA&q=yosemite+l2tp+client+screenshot&oq=yosemite+l2tp+client+screenshot&gs_l=img.3...31467.32993.0.33458.4.4.0.0.0.0.0.0..0.0....0...1c.1.64.img..4.0.0....0.DwZEmd9cG_Q#imgrc=3iY8yVfiQaz1oM:

The URL address came up as not secure and I opened another tab and copied and paste the same URL in the tab and it came up secure. I noticed the SHA256 finger print do not match. See enclosed

Hi mace2, in Google Images results, the mixed content warning will appear the first time you load an image on an insecure address (HTTP instead of HTTPS) and it will not go away until you reload the page. Even after you navigate away from that particular image, Firefox keeps it in the memory cache for the page and the lock retains the warning icon.

In your search, I found an example of such an image, attached.

The little thumbnail images do not trigger it because those are generated and stored by Google and accessed using an HTTPS connection. However, it's an unavoidable problem that viewing images at their original size or from their original source can cause this problem because many sites still do not use HTTPS. Considering that you aren't conducting any sensitive transactions when you are using image search results, the risk associated with insecure images is probably not high enough to justify excluding them: blocking Firefox from loading those images would make the results page much less useful.

Hi jscher2000, The problem is there is no insecure content on the url

https://www.google.com/search?biw=1280&bih=613&tbm=isch&sa=1&ei=pnWFW_b6EZHWsAHkkoXoDA&q=yosemite+l2tp+client+screenshot&oq=yosemite+l2tp+client+screenshot&gs_l=img.3...31467.32993.0.33458.4.4.0.0.0.0.0.0..0.0....0...1c.1.64.img..4.0.0....0.DwZEmd9cG_Q#imgrc=3iY8yVfiQaz1oM:

I have tried going to the same address multiple times and it continues to come up secure. for some reason that single moment caused the insecure result. What is also strange is the web site appear identical but has a different sha256 hash.

I have no explanation for the mixed content warning other than what I observe myself from time to time and mentioned before.

As for the certificates being different, perhaps you happened to hit a different server one time. I don't know how Google manages its data center.

  1. 1
  2. 2