The Google Chrome team will be running an experiment this week in an attempt to find out solutions in an HTTPS problem which the Mozilla Foundation also tried to resolved last year.
The problem that Google is trying to solve in Chrome is called "mixed content". content), which Google describes as:
Mixed content occurs when an original HTML (a web page) is loaded over a secure HTTPS connection, but there are resources (such as images, videos, css, scripts) που φορτώνονται μέσω μιας μη ασφαλούς σύνδεσης HTTP. Αυτό ονομάζεται μεικτό περιεχόμενο επειδή φορτώνεται τόσο το HTTP περιεχόμενο όσο και το HTTPS στην ίδια σελίδα. Τα σύγχρονα προγράμματα περιήγησης εμφανίζουν προalerts for this type of content to indicate to the user that this page also contains unsafe content.
In recent years, mixed content is a big problem for browser makers and websites using HTTPS.
Content browser mixed content bugs, in addition to preventing users from having full access to a site, have frightened and many webmasters who are thinking of changing to HTTPS, who do not want to lose clicks. Dealing with mixed content errors in web browsers is probably the last major hurdle to getting all administrators to switch to HTTPS. So this week, Google engineers started an experiment in Chrome by setting the browser to automatically upgrade any mixed content to full HTTPS. Google Chrome will do this by secretly changing the URL of unencrypted links (images, videos, css, scipts) from HTTP to HTTPS. If the same file exists with an HTTPS connection, then everything will work fine. If there isn't, then Chrome will log the error and run one of the many scripts configured for this experiment (analytically here). At this time, Google intends to run the above experiment on one percent of all Canary Chrome users who have enabled: chrome: // flags / # enable-origin-trial flag
