Chrome version 79 released on December 10, 2019
Chrome 80 update in January
Then the final version, Chrome 81 in February 2020
Chrome 80 Update
Major impacts on websites are to be expected from Chrome 80. Starting in January and the arrival of the Chrome 80 update, Google's default browser will block so-called "mixed" audio and video conten all mobile number list In other words, even if your site is HTTPS secure, if this content is still loaded via an unsecured HTTP connection, it will lower the security level displayed for your website. Images loaded via HTTP will still be displayed. New criteria to take into account in web design !
Chrome 81 Update
Then, Chrome 81 will be implemented in February 2020 with more drastic measures: this Chrome update will simply block all content loaded via an HTTP protocol (mixed content), including images . Chrome will nevertheless attempt to automatically upgrade them to HTTPS before taking this measure.
Consequences
Chrome will display security messages when opening websites. The “not secure” message will have a significant negative impact on your site’s reputation, user experience, and therefore traffic. This will likely cause your revenue to plummet if you own an e-commerce site!
made at imgflip.com
Before going any further, let's go over the main technical terms that are important to understand for the rest of this article.
HTTPS: definition
HTTPS (Hyper Text Transfer Protocol Secure) is a mechanism that allows your user's browser to connect securely to your website . In HTTPS, the sensitive data that your user shares with your website is encrypted , meaning it is completely protected.
HTTP: definition
Conversely, an HTTP connection is said to be unsecured because it runs the potential risk of hacking or data spying. In concrete terms, in HTTP, each time an Internet user enters personal data into a website, this information is transferred to your server in the form of “readable” text. Malicious and well-equipped hackers would have no trouble getting their hands on this data.
Mixed Content: Definition
Mixed content, as the name suggests, is any type of content that uses both HTTP and HTTPS protocols. This type of content is typically created when a regular HTML page is loaded over HTTPS but other elements on that page like images and videos are over an unsecured HTTP connection.
Mixed Content Cases and Examples
Case 1 – Secure connection: You are ready for Chrome 80/81 update
If your web page is fully secure without mixed content, then you will see this message when you click on the small padlock. You can leave this article, you are safe.
Chrome 81 update
This means that the page in question, as well as the various elements that compose it, are secure.
Case 2 – connection not completely secure: Chrome 80/81 concerns you directly!
Now let’s see what a mixed content warning looks like. You can spot this warning when the padlock icon seen earlier changes to a small “i”.
Chrome 80 update mixed content
As Chrome explains, the connection is not completely secure. This website uses a secure connection protocol (HTTPS) as indicated by “Certificate (Valid)”, but the presence of an insecure image loaded via an insecure HTTP protocol makes it potentially dangerous.
Here are some common causes of mixed content:
An image present in one of your articles or widgets that points to HTTP ( http://votredomaine.com/image.png)
Embedded video scripts on your website using HTTP instead of HTTPS.
Consider doing a 301 redirect from HTTP to HTTPS if some pages on your website are still in HTTP.
Case 3 – Unsecured connection: Take action immediately
In the worst case scenario, if you haven't yet migrated your website to HTTPS, you'll see this obvious security message right next to your URL:
chrome 81 security update
In this case, your website's protocol is not secure and you will run the risks mentioned at the beginning of the article. In addition, this message does not indicate the possible external elements that are also not secure. You must therefore imperatively switch to an HTTPS protocol (call your web developer now!), and then check the status of your connection to ensure that all the elements of your site work in HTTPS.
If you have a WordPress site, remember to perform a WordPress update to ensure a secure connection.
Take the test before updating Chrome 81
There are several ways to detect if and where your site contains mixed content. For example, you can try the sitecheck checker .
If your site contains mixed content, you will see a result like this:
mixed content chrome update
