04 November 2015 12:15
New Chrome security policy: powerful features will be removed on insecure origins
by 1 otherGoogle recently announced a security policy change that will impact future versions of the Chrome browser. Chrome is already warning that support to powerful features on insecure origins (HTTP) is deprecated, and according to recent announcements the removal will take place soon.
The impact of Google’s new Chrome security policy on WebRTC | TokBox Blog
After we published this post Google announced that they are pushing back the release date of the HTTPS security change. They’re estimating that it will now be released to production in December 2015.
04 November 2015 12:00
Deprecating Powerful Features on Insecure Origins - The Chromium Projects
(via)
As with gradually marking HTTP as non-secure, we expect to gradually migrate these features to secure-only, based on thresholds of usage, starting with lowest usage and moving towards higher. We also expect to gradually indicate in the UX that the features are deprecated for non-secure origins.
1
(3 marks)
