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 track down mixed content or insecure content

    What to do when you don’t get the green lock As a first step, you should check if the mixed content fixer is active on your site. You can see...
  • Disabling ssl for one page only

    The problem: services that don’t support SSL I think the best way to go is to get your entire site on SSL. But sometimes there are services that are not...
  • 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...
  • How to check if the mixed content fixer is active

    Really Simple SSL inserts a marker “data-rsssl” in the websource as a way to check if it’s working. If it it’s there the mixed content fixer is active. Really Simple SSL...