For convenience, the developers have posted a roadmap for innovations with blocking mixed content: iso, will fall under the lock, and everything will end in the version of Chrome 86, which will be released in October 2020, where all downloads of mixed content, that is, all file types, will be blocked. apk, etc.įurther, other types of files, such as. At first (from the version of Chrome 82, which will be released in April 2020), the Chrome browser will notify, but only in future versions it will already block executable files, for example. But don’t worry - we still have time to fix all the errors of mixed content. This way, developers will block all insecure resources on secure HTTPS pages. This request has been blocked the content must be served over HTTPS. Mixed Content: The page at '' was loaded over HTTPS, but requested an insecure favicon ''. This content should also be served over HTTPS. Yes, friends, what is so far showing as warning or an error in the developer console will be blocked soon: Mixed Content: The page at '' was loaded over HTTPS, but requested an insecure image ''. Google Chrome developers wrote on their blog that they would block the "download of mixed content" on HTTPS-protected pages with resources on HTTP.
0 kommentar(er)
