On Sun, 23 Jul 2000, Patrick Michael Kane wrote:
> * Jeff Norman ([EMAIL PROTECTED]) [000723 03:28]:
> >
> > I'm pretty sure that this will accomplish what you're looking for:
> >
> > <VirtualHost 192.168.0.1:80 192.168.0.1:443>
> > ServerName www.example.com
> >
> > Necessary directives for mod-SSL to work under normal conditions
> > All sorts of frequently changing directives
> > </VirtualHost>
>
> Unfortunately, no. That will start up an SSL server on both ports 80 _and_
> 443, which causes all sorts of problems.
>
> Any other thoughts?
Consider using three virtual hosts. The third virtual host does nothing but
provide content. Use mod_rewrite to proxy requests from your port 80 and
port 443 virtual hosts to the third virtual host providing the content.
Let the third virtual host be responsible for redirecting to the port 443
virtual host when required. The port 80 host would be nothing but a series
of mod_rewrite statements. The port 443 host would contain mod-rewrite and
mod_ssl statements. All content related directives would be in the third
hidden host.
Merton Campbell Crockett
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
