Unlike the new site, we’re going to have files, images and other content that we uploaded previously to a non secure server.
That means the html that is going to pull in that image thing might look like this instead.
There’s an S missing after the http – and as the page attempts to load in the visitors browser their browser is going to see that some of the elements (in this case the picture) are not coming from a secure place. Their browser is going to throw them up a warning.
This is called “Poisoning The Well” and it’s something we need to avoid doing at all costs when we are secure.
So the fix is that you now have to go back to each of your posts, each of your pages, each of your headers, footers and widgets. You need to check and change the url of every single thing that is being pulled in to build your site or page. This isn’t just images, this could be CSS, this could be scripts, this could be embed codes. It’s time consuming for sure and that’s why it’s easier to start with a new site.
Posted in: HTTPS, SSL and making your site Secure