[mgkimsal]

I think this is meant to deal with non-SSL content hosted outside of your own domain, right? As the earlier posted pointed out, you can just get an SSL cert and DIY much cheaper. If it's to deal with non-SSL content hosted by someone else, I'm assuming you're proxying the content?

Might you still get those errors anyway if some javascript on the page makes a request for non-SSL content?

[diamondsea]

Correct, it's for showing off-site content on your own secure pages, such as a portal site showing a photo-of-the-day from another site or an RSS feed containing images.

Yes, you could roll your own solution, but this is, well, easier and lots of non-programmer admins might have trouble with it. This is just a simple way to access that site without having to write or load scripts onto your server.

Right now, it's just a straight passthrough (GET/ECHO) of the requested URL, nothing fancy. If you request an HTML or RSS page it will try some basic munging of the content to change the non-SSL links to reroute them through the fixssl system. I could expand on those if there's any interest in the service.