Mark H. Wood wrote:
We have HTTPD 2.2 with several IP-based VirtualHost definitions. Now
one of our partners wants to add some name-based vhosts, and it would
be convenient to just keep using the same address:port as their
existing application. What I mean to do is just add another
VirtualHost for each application, a NameVirtualHost fingering the
address:port pair, and ensure that the existing vhost is parsed first
so it becomes the default for no-name requests. Will this work? Am I
nuts?
The description of the way the address:port name lists are built and
used seems to imply that I can get away with this. But then there's a
bit about name- and IP-based vhosts being unable to "interfere", which
makes me uncertain.
I'm not sure you can combine name-based and IP-based either.
But assuming a number of things, you could always run a separate Apache
httpd, listening on their IP only, and having only name-based vhosts.
No ?
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [email protected]
" from the digest: [email protected]
For additional commands, e-mail: [email protected]
