Google Online Security Blog: No More Mixed Messages About HTTPS

Security Blog

The latest news and insights from Google on security and safety on the Internet

No More Mixed Messages About HTTPS

3 ottobre 2019

Posted by Emily Stark and Carlos Joan Rafael Ibarra Lopez, Chrome security team Update (04/06/2020): Mixed image autoupgrading was originally scheduled for Chrome 81, but will be delayed until at least Chrome 84. Check the Chrome Platform Status entry for the latest information about when mixed images will be autoupgraded and blocked if they fail to load over https://. Sites with mixed images will continue to trigger the “Not Secure” warning. mixed contentprogressChrome will gradually move to blocking all mixed content by default Timeline

In Chrome 79, releasing to stable channel in December 2019, we’ll introduce a new setting to unblock mixed content on specific sites. This setting will apply to mixed scripts, iframes, and other types of content that Chrome currently blocks by default. Users can toggle this setting by clicking the lock icon on any https:// page and clicking Site Settings. This will replace the shield icon that shows up at the right side of the omnibox for unblocking mixed content in previous versions of desktop Chrome.

Accessing Site settings, from which users will be able to unblock mixed content loads in Chrome 79.

In Chrome 80, mixed audio and video resources will be autoupgraded to https://, and Chrome will block them by default if they fail to load over https://. Chrome 80 will be released to early release channels in January 2020. Users can unblock affected audio and video resources with the setting described above.

Also in Chrome 80, mixed images will still be allowed to load, but they will cause Chrome to show a “Not Secure” chip in the omnibox. We anticipate that this is a clearer security UI for users and that it will motivate websites to migrate their images to HTTPS. Developers can use the upgrade-insecure-requests or block-all-mixed-content Content Security Policy directives to avoid this warning.

Omnibox treatment for websites that load mixed images in Chrome 80.

In Chrome 81, mixed images will be autoupgraded to https://, and Chrome will block them by default if they fail to load over https://. Chrome 81 will be released to early release channels in February 2020.

Resources for developers

Use Content Security Policy and Lighthouse’s mixed content audit to discover and fix mixed content on your site.

See this guide for general advice on migrating servers to HTTPS.

Check with your CDN, web host, or content management system to see if they have special tools for debugging mixed content. For example, Cloudflare offers a tool to rewrite mixed content to https://, and WordPress plugins are available as well.

Nessun commento :

Posta un commento

Etichette

Archive

2024
- dic
- nov
- ott
- set
- ago
- lug
- giu
- mag
- apr
- mar
- feb
- gen

2023
- dic
- nov
- ott
- set
- ago
- lug
- giu
- mag
- apr
- mar
- feb
- gen

2022
- dic
- nov
- ott
- set
- ago
- lug
- giu
- mag
- apr
- mar
- feb
- gen

2021
- dic
- nov
- ott
- set
- ago
- lug
- giu
- mag
- apr
- mar
- feb
- gen

2020
- dic
- nov
- ott
- set
- ago
- lug
- giu
- mag
- apr
- mar
- feb
- gen

2019
- dic
- nov
- ott
- set
- ago
- lug
- giu
- mag
- apr
- mar
- feb
- gen

2018
- dic
- nov
- ott
- set
- ago
- lug
- giu
- mag
- apr
- mar
- feb
- gen

2017
- dic
- nov
- ott
- set
- lug
- giu
- mag
- apr
- mar
- feb
- gen

2016
- dic
- nov
- ott
- set
- ago
- lug
- giu
- mag
- apr
- mar
- feb
- gen

2015
- dic
- nov
- ott
- set
- ago
- lug
- giu
- mag
- apr
- mar
- feb
- gen

2014
- dic
- nov
- ott
- set
- ago
- lug
- giu
- apr
- mar
- feb
- gen

2013
- dic
- nov
- ott
- ago
- giu
- mag
- apr
- mar
- feb
- gen

2012
- dic
- set
- ago
- giu
- mag
- apr
- mar
- feb
- gen

2011
- dic
- nov
- ott
- set
- ago
- lug
- giu
- mag
- apr
- mar
- feb

2010
- nov
- ott
- set
- ago
- lug
- mag
- apr
- mar

2009
- nov
- ott
- ago
- lug
- giu
- mar

2008
- dic
- nov
- ott
- ago
- lug
- mag
- feb

2007
- nov
- ott
- set
- lug
- giu
- mag

Feed

Give us feedback in our Product Forums.

Google
Privacy
Terms