3 ms·
I came back to reply to myself that there is now a Content Security Policy header to deal with this exact situation: https://w3c.github.io/webappsec/specs/upgr
by snowwrestler 12y ago
I came back to reply to myself that there is now a Content Security Policy header to deal with this exact situation:
https://w3c.github.io/webappsec/specs/upgrade/ https://w3c.github.io/webappsec/specs/upgrade/
It is included in the Chrome 43 beta [1], and Firefox is working on it as well [2]. This is excellent news for folks looking to upgrade existing sites to HTTPS.
[1] http://blog.chromium.org/2015/04/chrome-43-beta-web-midi-and-upgrading.html http://blog.chromium.org/2015/04/chrome-43-beta-web-midi-and...
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1139297 https://bugzilla.mozilla.org/show_bug.cgi?id=1139297