Chrome 43 Should Help Batten Down HTTPS Sites

River Tam writes The next version of Chrome, Chrome 43, promises to take out some of the work website owners — such as news publishers — would have to do if they were to enable HTTPS. The feature might be helpful for publishers migrating legacy HTTP web content to HTTPS when that old content can't or is difficult to be modified. The issue crops up when a new HTTPS page includes a resource, like an image, from an HTTP URL. That insecure resource will cause Chrome to flag an 'mixed-content warning' in the form of a yellow triangle over the padlock.

Comments

Hello, Chrome

[Ignacio]

Welcome to 2013.

Re:Is this supposed to be a new thing?

[Culture20]

Firefox and IE copied this feature so fast they went back in time.

Chrome broke my VPN

[140Mandak262Jamuna]

When it rains it pours. I am battling a serious RAID controller failure at my work desktop. At least I could go home, use VPN to access some common team servers to do some work. Lo, and behold! St Murphy, the patron saint of all things barfing, decides to step in at this critical juncture. Chrome decides to cut Java. Our wonderful IT had bought VPN software that relies on java plug-in in the browser. OK firefox will come to my rescue, so I thought. But St Murphy had anticipated my move.

When everything fails, you sell your soul to Satan and decide to fire up, gasp, internet explorer. For some odd reason it manages to get past all the hurdles gets the network extender running. Satan is laughing at St Murphy. St Murphy never loses, his revenge will come soon, and it will be swift.

In the meantime, caught as a mere pawn in the eternal battle between Satan and St Murphy I am ruing my fate and belly aching in slashdot.