November 26, 2020
Chrome to block unsecured content on https pages

Google Plans to Block Unsecure Content on HTTPS Pages by Default

Google reveals its plans to automatically block unsecured content on encrypted HTTPS pages by default, in a gradual roll out…

Encrypted, HTTPS pages have largely replaced unsecured HTTP pages as the default choice for sending resources over the web. The big difference is the former is secure, while the latter has no such protection.

Google Chrome to Block Unsecured Content on HTTPS Pages

Google already marks unsecured pages or HTTP connections as “Not Secure.” The company began implementing the warning starting with Chrome version 68.

Now, Google says it plans to tackle mixed content. That is, using various resources, such as images, audio, and video, through HTTP on otherwise, secured HTTPS pages.

Google will start the practice with the release of Chrome version 79. The search giant will begin gradually blocking mixed content. With version 80, Google will block mixed audio and video by default.

Google writes on its official Chromium Blog:

“…we’re announcing that Chrome will gradually start ensuring that https:// pages can only load secure https:// subresources. In a series of steps outlined below, we’ll start blocking mixed content (insecure http:// subresources on https:// pages) by default. This change will improve user privacy and security on the web, and present a clearer browser security UX to users.”

Owen E. Richason IV

Covers social media, apps, search and like news. History buff, movie and theme park lover. Blessed dad and husband. Owen is also a musician and is the founder of Groove Modes.          

View all posts by Owen E. Richason IV →