loloyd,
Sorry, but we don't see the problem here. It's up to the web site designer to make pages serve everything from a HTTPS request to avoid that situation. The server can do nothing if you have hard coded a http:// inside your page.
So for example, instead of using:
<IMG SRC="http;//mysite/test.jpg">
write:
<IMG SRC="/test.jpg">
The second chunk will never raise any warning and will work regardless of your domain name and the protocol you're going to choose when deploying the site.
