SSL port-based virtual how-to?

[Jay States <js...@mac.com>]

I was reading the stronghold .pdf and it says that port-based virtual 
hosting can not be mixed with name-based hosting directives.  One 
problem solved, but wait.  I remove the NameVirtualHost tags and the 
next problem is this:

[Tue Jul 16 18:09:26 2002] [warn] VirtualHost 24.222.3.138:444 overlaps 
with VirtualHost 24.222.3.138:444, the first has precedence, perhaps you 
need a NameVirtualHost directive

Solutions?

Again Thanks everybody, special shout to Mark

J


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: SSL port-based virtual how-to?

[Mark Mentovai <ma...@mentovai.com>]

Jay States:
> I was reading the stronghold .pdf and it says that port-based virtual 
> hosting can not be mixed with name-based hosting directives.

Are you using Stronghold?

You are free to mix name-based and IP address/port-based virtual hosting within 
the same server configuration, but not on the same IP address and port.  That's 
why you have multiple Listen directives, but only one NameVirtualHost 
directive.

> One 
> problem solved, but wait.  I remove the NameVirtualHost tags and the 
> next problem is this:
> 
> [Tue Jul 16 18:09:26 2002] [warn] VirtualHost 24.222.3.138:444 overlaps 
> with VirtualHost 24.222.3.138:444, the first has precedence, perhaps you 
> need a NameVirtualHost directive
> 
> Solutions?

You can't define multiple virtual hosts on the same IP address and port unless 
they're name-based virtual hosts and you have used NameVirtualHost.  If you try 
to do so, the first such definition will mask any future ones.

As we've established, you can't use name-based virtual hosting with SSL.  For 
each SSL virtual server, you will need to use a different port.  You will need 
one Listen directive for each port ("Listen 24.222.3.138:443", "Listen 
24.222.3.138:444", etc.), no NameVirtualHost directives, and one <VirtualHost> 
block for each port.  ("<VirtualHost 24.222.3.138:443>", "<VirtualHost 
24.222.3.138:444>", etc.)  Based on your error, it would seem that you have 
more than one definition for "<VirtualHost 24.222.3.138:444>".

Because you can use name-based hosting for the non-SSL virtual servers, you 
will use a single port with NameVirtualHost.  You need "Listen 24.222.3.138:80" 
and then only one NameVirtualHost directive, "NameVirtualHost 24.222.3.138:80", 
combined with a series of "<VirtualHost 24.222.3.138:80>" blocks that define 
each virtual server.

> Again Thanks everybody, special shout to Mark

No problem at all, glad to help.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org