@barry13 @sesser @ others who know more about this stuff than I do... Not long ago, I switched this site to https. That has proven to be a huge pain in the neck. While most members post secure content (thread attachments, Flickr https images, etc), some continue to post images from non-secure (http) hosting sites. This leads to mixed content warnings in browsers, and some members browsers may be set up to block non-secure content. To get around this issue, I've made several attempts to setup an image proxy that would retrieve all externally hosted images and temporarily host those images here so they could be made secure. Besides getting rid of the mixed content warnings, this also makes the site more secure, preventing certain forms of cookie stuffing. However, the image proxy has proven extremely costly (paying developers, upgrading the server, spending my own time), and I haven't been able to get it just right. Certain images don't show, either for known reasons (slow origin) or unknown ones (gremlins). So I'm faced with three options: 1) Keep trying to get the image proxy right (but I'm running out of time and money) 2) Change the sites back to http 3) Leave the sites https and accept the occasional mixed content warnings I'm leaning towards #3 (in fact that is the current state). What do you think?