In 2020, Google will use updates to its Chrome browser to block content (such as images and videos) because it is not securely loaded. The calendar was announced in February.
The announcement goes back to the beginning of November 2019. In order to protect a little more the Internet user when surfing the web, Google will be less accommodating with regard to what is called mixed content, ie content (such as images or videos) which are not loaded in a secure way on web pages.
These secure pages are called HTTPS (HyperText Transfer Protocol Secure) pages, because they benefit from a layer of protection thanks to encryption. The link between the internet user and the site visited is then encrypted, which is essential, especially when buying online, accessing their e-mail or bank account. For several years, the web has experienced a global switch to HTTPS.
However, there are still sites that do not use this protective layer. These are sites in HTTP (HyperText Transfer Protocol). But there is also an intermediate scenario, where secure pages (HTTPS) load content that is not (HTTP). This is why we speak of mixed content, because they can be alongside other files which are loaded with security.
At the time, Google had a calendar taking place in three phases, each of which corresponds to the release of a new version of its web browser: Chrome 79 (December 10), Chrome 80 (February 4) and Chrome 81 (March). Three months later, the Mountain View company released an updated plan for blocking mixed content in Google Chrome.
What calendar for mixed content on Google Chrome?
The new schedule is as follows:
from Chrome 81 (March 2020), a warning will appear on the browser console for all types of mixed content.
With Chrome 82 (April 2020), a warning concerning executable files (.exe, .apk, etc.) which are not loaded in security will be directly visible by the Internet user.
Sure Chrome 83 (June 2020), these unsecured executable files will be blocked by the browser. The warning will then slip into the archives and disk images (.zip, .iso, etc.).
For Chrome 84 (August 2020), the blocking will be extended to archives and disk images. The warning will then concern all the other files (.pdf, .docx, etc.), except for images, videos, sounds and text formats.
The exit of Chrome 85 (September 2020) will raise the warning to the level of content that had been previously saved, namely images, videos, sounds and text formats. The other files will be blocked.
Finally, with Chrome 86 (October 2020), the blocking will impact all mixed content, without exception.
This calendar is valid for the desktop versions of Google Chrome, ie Windows, macOS and Linux. For mobile versions, ie Android and iOS, the transition will simply be shifted from one version. The warning visible to the mobile user will arrive with Chrome 83 and, consequently, the global blocking of mixed content will be effective with Chrome 87.
The following table summarizes the Google calendar:
Google recalls that these chances can be overcome by website grants relatively easily: it is enough to migrate their pages completely to HTTPS, and there will be no warning or blocking. It takes some effort, but not only do they have a few more months to make their arrangements, but more importantly, they have a timetable for them to prioritize their actions.
Share on social networks