Joined
·
3,038 Posts
Heya Pepe!see there. I need to pay more attention to what schwim posts. :thumbup
I suck at the internet. :brownbag
Was I completely off schwim?
I may have assumed the "s" in "https" was a problem I ran across awhile ago and have been working under a false assumption so I figure it's worth asking.
FWIW, I greatly appreciate your knowledge and your willingness to share and educate.
Although serving secure images across domains and over an insecure connection can be problematic, if you're serving https images on an http connection (https://image on http://site) and it's not working, it's almost always caused by the host you're trying to serve secure content from not having a valid SSL cert. With sites like Dropbox, however, you can pretty much count on it working.
The more common problem is serving non-secure images on a secure connection (http://image showing on https://site). It's actually your browser keeping it from displaying as a security measure. an SSL connection is a guaranteed encrypted connection and any non-encrypted information(an image servered over http, for instance) is kept from displaying. That's the issue you're probably thinking of as it's the most common.
As long as the SSL cert is valid, you can always display an https:// image, regardless of whether you're viewing it via http or https. That's why you see the image hosting sites always using https. That way they can be sure the images will display across either connection method.