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>
Jazz
On Sat, 22 Jul 2000, Patrick Michael Kane wrote:
> Hello!
>
> I've been using mod_ssl for quite some time now, but one thing has always
> bugged me. Is there a way to avoid duplicating the entire
> <VirtualHost></VirtualHost> section when I create an SSL enabled server for
> a VirtualHost that is already serving HTTP?
>
> To whit, if I have:
>
> <VirtualHost 192.168.0.1:80>
> ServerName www.example.com
>
> All sorts of frequently changing directives
> </VirtualHost>
>
> Currently when I need an SSL version, I'll just copy this VirtualHost
> section, change the port and enable SSL. This creates a maintenance
> headache, however, since any changes to this site now have to be made twice.
>
> Is there any way to avoid this duplication?
>
> Best Wishes,
> --
> Patrick Michael Kane
> <[EMAIL PROTECTED]>
> ______________________________________________________________________
> Apache Interface to OpenSSL (mod_ssl) www.modssl.org
> User Support Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
>
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
