4 ms·
You also need to scrub the existing site for content embedded with HTTP links, because active mixed content is blocked by default in Firefox and Chrome (as it s
by snowwrestler 12y ago
You also need to scrub the existing site for content embedded with HTTP links, because active mixed content is blocked by default in Firefox and Chrome (as it should be).
We did our first site HTTPS-only the exact way you describe, but didn't anticipate half our embedded content disappearing. The situation is getting better fast, but even a year ago a number of pretty well-known services like Scribd and Storify didn't fully work over HTTPS.
Video is the worst; every TV network has its own embeddable video player, and most of them did not work at all over HTTPS until very recently. Again, that's getting better pretty fast.
- snowwrestler 12y agoI 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