Fix Mixed Content Warnings and Blocked Content with HTTP/HTTPS Remover
When a site is under SSL—meaning all its links start with
https:// rather than
http://—then that site cannot load insecurely referenced resources: files, from any location, that start with
Many resources can be accessed either securely or insecurely: for example, Google Fonts will serve Open Sans at either
https://fonts.googleapis.com/css?family=Open+Sans. But when you then put your site under SSL, those insecure
http://-style links all break, and those resources go missing and throw mixed content warnings. In the Chrome Inspector, this issue will produce one error message like the following for each piece of blocked content:
Mixed Content: the page at
[page link starting with https://]was loaded over HTTPS, but requested an insecure
[resource link starting with http://]. This request has been blocked; the content must be served over HTTPS.
Now: What to do if there are tons of these bad
http://-style links in a third-party plugin? You can’t edit the files directly, unless you want to permanently prevent the plugin updating—and go deep-diving into someone else’s likely questionable plugin code.