Didn’t help with my images

After investigating, this is the image that’s causing the mixed content warning:

Looking at the source code, here’s a snippet of what you currently have:

<section class="section-contact" id="section-contact" style="background-image: url( http://fourfincreative.com/online/wp-content/uploads/2014/03/iStock_000045557738_Small.jpg);">

This issue can be easily fixed on your end by changing manually to the following:

<section class="section-contact" id="section-contact" style="background-image: url(//fourfincreative.com/online/wp-content/uploads/2014/03/iStock_000045557738_Small.jpg);">

Q: Why doesn’t Remove HTTP remove the protocol in this case?
We only have protocols removed from the following sources:
script,link,base,img,form,a,meta,iframe,svg

In previous versions, we did have a more aggressive algorithm to remove any reference of http:// or https://. However, we discovered that it was too aggressive and caused issues with some plugins.

I also see that your other <section> tags use protocol-relative URLs:

<div class="services-bg" style="background-image: url(//fourfincreative.com/online/wp-content/uploads/2014/03/smallboat.jpg);"></div>
<div class="blog-bg" style="background-image: url( '//fourfincreative.com/online/wp-content/uploads/2014/03/blog.jpg' );"></div>

In your case, it would be quicker to make the fix on your end since it’s only one image that’s causing the issue. If this is all content-related, you can ensure that all of your links are pointing to HTTPS by following these steps.

Until then, if we can figure out a way on our end to update our algorithm to also fix it, we will definitely push it in the next update.

• This reply was modified 7 years, 11 months ago by Fact Maven.