← Back to release summary

Blocking insecure downloads from secure (HTTPS) contexts

Category
Security
Type
Feature removal
Status
Browser Intervention (Chrome 84)
Intent stage
Shipped

Summary

Chrome intends to block insecurely-delivered downloads initiated from secure contexts ("mixed content downloads"). Chrome will begin warning on, then blocking, progressively more mixed content downloads until all such downloads are silently blocked.

Motivation

Downloads over insecure contexts present a risk to users. Once downloaded, a malicious file can circumvent any protections Chrome puts in place. Further, Chrome does not and can not warn users by downgrading security indicators on secure pages that initiate insecure downloads, as it does not reliably know whether an action will initiate an insecure download until the request is made.

Standards & signals

Docs: https://blog.chromium.org/2020/02/protecting-users-from-insecure.html https://docs.google.com/document/d/1BRvhtleXB91bkTAq4Xde9vzDoLbcwIuaxaSko3eUQ14/edit?usp=sharing

Explainers: https://github.com/mikewest/webappsec-mixed-content/blob/master/proposed-level-2-roadmap.md https://github.com/mikewest/webappsec-mixed-content/pull/2

View on chromestatus.com