On Fri, Mar 13, 2009 at 12:19 PM, Mark H. Wood <mwood@xxxxxxxxx> 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? Yes, the default vhost in a set of NameVirtualHosts should suit you nicely. -- Eric Covener covener@xxxxxxxxx --------------------------------------------------------------------- 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: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|