Chrome blocks non-HTTPS based content
The most popular web browser will soon start blocking any form of non-HTTPS based content from January 2020. This decision by Google will also affect individual elements of web pages. Some examples are ads that are often served over insecure HTTP.
Google advises publishers of web content to check their websites for individual elements such as audio, video, images, scripts, styles, iframes, etc. According to Google, many websites have “mixed” content, meaning that while the website uses an HTTPS connection, many elements of the website use HTTP, which is a security compromise.
Google has already pressured publishers to switch to HTTPS by tagging any page that does not use it as insecure. The company claims that now over 90% of web browsing time is done via HTTPS.
Not only Chrome, but other modern browsers now display a warning message for pages with insecure content (non-HTTPS). They also block mixed content (iframes, scripts), but video, audio and images are still allowed to be moved.
For that reason Google, in Chrome 79 (to be released in December) will block content and give users the option to allow non-secure content on a per-site basis.
In Chrome 80 (to be released in January 2020), all pages with “mixed content” HTTP and HTTPS will be titled insecure. The user will have the option to allow the movement of insecure material such as video and audio.
You can read another interesting, technology-related article by clicking here.
Author: PC-GR
The World of Technology
