Sunday, May 13, 2012

How to remove Chrome's insecure content alert

I am developing few sites using https://sites.google.com, but was so annoyed just recently of Chrome's "This Site has insecure content (Don't load, Load anyway)" alert in the pages of all my websites. One blogger wrote that I need to press CTRL+SHIFT+j to see what was causing it. Surprised, it was caused by google sites themselves.


Can you imagine the following causes--it's almost all google's or at least the word "google" such as "http://pagead2.googlesyndication.com/pagead/js...show_ads_impl.js".


The page at about:blank displayed insecure content from http://pagead2.googlesyndication.com/pagead/ads?client=ca-pub-5117933205504599&format=728x90_as&output=html&h=90&w=728&lmt=1336946874&host=pub-6693688277674466&ad_type=text_image&color_bg=FFFFFF&color_border=FFFFFF&color_link=000000&color_text=444444&color_url=0033CC&flash=11.2.202&url=https%3A%2F%2Fsites.google.com%2Fsite%2Fstrengthenedbythisverse%2F&dt=1336975683109&bpp=4&shv=r20120502&jsv=r20110914&prev_fmts=120x600_as&correlator=1336975683106&frm=20&adk=1335628509&ga_vid=1546748914.1336975221&ga_sid=1336975369&ga_hid=1490068524&ga_fc=1&u_tz=-480&u_his=13&u_java=1&u_h=768&u_w=1024&u_ah=728&u_aw=1024&u_cd=32&u_nplug=7&u_nmime=13&dff=arial&dfs=12&adx=199&ady=358&biw=1008&bih=667&oid=3&ref=https%3A%2F%2Fsites.google.com%2Fsite%2Fstrengthenedbythisverse%2Fsystem%2Fapp%2Fpages%2Fadmin%2Fappearance%2FpageElements&fu=0&ifi=2&dtd=642&xpc=XvnqvfMIXT&p=https%3A//sites.google.com.
The page at https://sites.google.com/site/strengthenedbythisverse/ ran insecure content from http://pagead2.googlesyndication.com/pagead/js/r20120502/r20120410/show_ads_impl.js.
2The page at https://sites.google.com/site/strengthenedbythisverse/ ran insecure content from http://pagead2.googlesyndication.com/pagead/expansion_embed.js.
The page at https://sites.google.com/site/strengthenedbythisverse/ ran insecure content from http://pagead2.googlesyndication.com/pagead/js/r20120502/r20120410/show_ads_impl.js.
The page at about:blank displayed insecure content from http://pagead2.googlesyndication.com/pagead/ads?client=ca-pub-5117933205504599&format=300x250_as&output=html&h=250&w=300&lmt=1336946874&host=pub-6693688277674466&ad_type=text_image&color_bg=FFFFFF&color_border=FFFFFF&color_link=000000&color_text=444444&color_url=0033CC&flash=11.2.202&url=https%3A%2F%2Fsites.google.com%2Fsite%2Fstrengthenedbythisverse%2F&dt=1336975683114&bpp=4&shv=r20120502&jsv=r20110914&prev_fmts=120x600_as%2C728x90_as&correlator=1336975683106&frm=20&adk=30073298&ga_vid=1546748914.1336975221&ga_sid=1336975369&ga_hid=1490068524&ga_fc=1&u_tz=-480&u_his=13&u_java=1&u_h=768&u_w=1024&u_ah=728&u_aw=1024&u_cd=32&u_nplug=7&u_nmime=13&dff=arial&dfs=12&adx=431&ady=983&biw=1008&bih=667&oid=3&ref=https%3A%2F%2Fsites.google.com%2Fsite%2Fstrengthenedbythisverse%2Fsystem%2Fapp%2Fpages%2Fadmin%2Fappearance%2FpageElements&fu=0&ifi=3&dtd=1430&xpc=ZFB4wjTJQx&p=https%3A//sites.google.com.
The page at https://sites.google.com/site/strengthenedbythisverse/ displayed insecure content from http://pagead2.googlesyndication.com/pagead/abglogo/adc-en-100c-000000.png.
The page at about:blank displayed insecure content from http://googleads.g.doubleclick.net/pagead/drt/s?v=r20120211.
The page at https://sites.google.com/site/strengthenedbythisverse/ displayed insecure content from http://pagead2.googlesyndication.com/pagead/abglogo/adc-en-100c-000000.png.
The page at about:blank displayed insecure content from http://googleads.g.doubleclick.net/pagead/drt/s?v=r20120211.
3The page at http://googleads.g.doubleclick.net/pagead/drt/s?v=r20120211 displayed insecure content from http://google.com/pagead/drt/ui.

I also followed "googleads.g.doubleclick.net" where one author (see hubpages) wrote in his page a blog entitled "What is http://googleads.g.doubleclick.net/ pagead/test_domain.js ? (By ) that his Kaspersky alerted him that this site was blocked due to password and credit card issues; but that an email from Kaspersky confirmed that it was just a false alarm, since this site was already bought by Google.

In one forum I followed the instruction of inserting the command-line option "--allow-running-insecure-content" and the message alert "insecure content" went away. (The reverse command in case you'll be interested is "--no-displaying-insecure-content"--if you want Chrome to go with its insecure content routine).

To insert the --allow-running-insecure-content command, go to Chrome's icon on your desktop (or at the start menu), right click, then go to Properties -> Shortcut, then Start in, and you'll find something like this: C:\Users\yourcomputername\AppData\Local\Google\Chrome\Application...at the end allow one space then paste or type: --allow-running-insecure-content.

Not the end of the story yet: Chrome continued to place a red mark on my "https" indicating that it just allowed, but the problem known as insecure-content is still there.

Others testified of a fully normal webpage browsing and total gmail insecure-content solution. But I was not as lucky. Of course, I will continue digging for other concrete solutions yet to this very annoying Chrome's security feature.


No comments:

Post a Comment