Running both a http port AND a https port

[openeyes]

I have an obscure use case wherein I need both a secure and an insecure port. Ultimately, subsonic is going to be reverse proxied to so it will be secure, but I have a need for both an insecure and a secure port. One of the big issues I have is that if I run an insecure port, I will get mixed content warnings as the scripts will try to load the http:// variant of my site, which will get blocked in chrome and firefox. Because of this, I am hoping to reverse proxy to the secure port for this application, and then have the insecure port as well for another application.

However, giving the arguments "--port=4040 --https-port=4141" will cause any connection to 4040 to be redirected to 4141.

Is there any way to avoid this?

[madhusker]

I have that too. Drives me nuts! Never could figure out how to fix it.