I was using Safari on OS X when I got the error.
Sorry for being dense, but could you elaborate on what I should learn from that thread you linked? Is there some kind of solution there, maybe if I was using Chrome, that I might have missed?
Sorry for being dense, but could you elaborate on what I should learn from that thread you linked? Is there some kind of solution there, maybe if I was using Chrome, that I might have missed?
The technically correct fix is for the site owner to modify the page to load all these resources over https when the page is accessed over https. Until they do that, as a workaround, you could install an extension like the one mentioned by fl3tch[1] to do it in your browser.
N.B. That only works if the resource is available over https, many are not. In that case there is no fix.
The easiest way to do that is with protocol-relative URLs. You're probably familiar with relative paths in URLs, e.g. if example.com/test/test.html loads an image at pics/pic1.png, it will really look in https://example.com/test/pics/pic1.png if you loaded it over https, or http: if you loaded over http.
Simple, right? Well, you can use the same idea for absolute paths and even resources from other sites! So if a different site links to the URL //example.com/test/pics/pic1.png (note the lack of protocol before the double-slash), then it will use https: if you loaded the page over https and http: if you loaded it using http.