In a series of steps outlined below, we’ll start blocking 'mixed content downloads' (non-HTTPS downloads started on secure pages). Today we’re announcing that Chrome will gradually ensure that secure (HTTPS) pages only download secure files. Developers who are otherwise able to do so are encouraged to transition to secure downloads as soon as possible to avoid future disruption. The text below has been updated to reflect this change.
User-visible warnings will start in Chrome 84. Console warnings on mixed downloads will begin as scheduled in Chrome 81.
These warnings, as well as subsequent blocking, will be delayed by two releases. Update (April 6, 2020): Chrome was originally scheduled to start user-visible warnings on mixed downloads in Chrome 82.
