Mixed content occurs when initial HTML is loaded over a secure HTTPS connection, but other resources (such as images, videos, stylesheets, scripts) are loaded over an insecure HTTP connection. This is called mixed content because both HTTP and HTTPS content are being loaded to display the same page, and the initial request was secure over HTTPS.
Requesting subresources using the insecure HTTP protocol weakens the security of the entire page, as these requests are vulnerable to man-in-the-middle attacks, where an attacker eavesdrops on a network connection and views or modifies the communication between two parties.Eventually, the presence of such content could even allow an adversary to take complete control of the affected page. Google explained that such content also affects the browser security UX. The browser could neither present it as HTTPS, nor HTTP. To further enhance the security of your network, one should consider using the services of a reliable service provider like Spectrum Internet.
As per the disclosed timeline, initially, Google will roll out settings for users to unblock mixed content on sites. This will take place with Chrome 79 releasing in December 2019.
Then, with Chrome 80, Google will block audio/video resources that fail to load over HTTPS by default. Users would still be able to unblock the content via given settings. However, it will allow the mixed images, where the browser will prompt the site as ‘Not Secure’.
Finally, with Chrome 81 coming in February 2020, Google will block mixed images as well.
For convenience, Google has shared detailed guides for migrating to HTTPS and preventing mixed content as well.
Let us know your thoughts in the comments.
