Quote:
Originally Posted by Avulon
I think the issue is that some pages are hosting objects which are being fetched by plain HTTP despite the page itself using HTTPS. this leads to warnings that the page isn't completely secure.
|
Yes, or mixed content as it's known being displayed on the same page. Page 2 of this thread is ok but not page 1. Why? I think that the answer might be in the image in Pete's signature in post 7. It is showing as HTTP unlike Phil's in post 2 which is showing as HTTPS. The problem will be the same on many pages across the site, if not with images then it will likely be with links.