Mixed content

My browser still gives mixed content warnings

If you still get mixed content warnings, you have to track down the cause.

If the mixed content fixer is working, the Really Simple SSL fixes all images, javascript, style links, @import urls and iframes with http links. In most cases, the mixed content is caused by http links in javascript (.js) or stylesheets (.css) that were included. The mixed content fixer cannot fix these.

Read this step by step article how to track down mixed content. After you’ve tracked down the .css file or .js file, you can change its source from http:// to //, which makes it fit for both protocolls.

If you have urls in your websource causing mixed content warnings that were not fixed, while the mixed content fixer was active, please let me know which html code caused this, so I can add it to the mixed content fixer.

Related Articles

  • How to check if the mixed content fixer is active

    The plugin shows some common issues on the configuration page. What to do when you see this one? The mixed content fixer is activated, but was not detected on the...
  • Parts of my site not loading

    Did you install Really Simple SSL on your site, and now some images, stylesheets, or external servcies are not loading? When a site is requested over the SSL protocol, the...
  • Plugin conflict force rewrite title Yoast

    * Update* This issue should be resolved in the 2.4 version. I left the Yoast check for now, but this warning will be removed in future versions. If you have...
  • How to exclude a url from the mixed content fixer

    It sometimes is necessary to exclude a certain url from the mixed content fixer. For those who don’t know already: the mixed content fixer in Really Simple SSL changes all...