ServerName sets the name for the server (as you'd expect). There can be only one per server. ServerAlias sets up additional non-canonical names for the server that it will pay attention to. There can be any number per server.
You have to have a Listen for every ip/port you want to respond to. You'll have to have a NameVirtualHost for every ip/port that you want to serve multiple vhosts from, based on host headers. cheers, barneyb On Wed, Feb 25, 2009 at 3:08 PM, Ian Skinner <[email protected]> wrote: > > Barney Boisvert wrote: >> Yeah, you bet. Just set the list of IP/ports in the VirtualHost >> directive (space separated), and add necessary ServerAliases: >> >> <VirtualHost 192.168.100.251:80 192.168.100.252:80> >> ServerName www.mentor.com >> ServerAlias mentor.com >> ServerAlias origin.mentor.com >> >> cheers, >> barenyb > > Thanks, I felt it should be possible. Before I go and confuse myself > with the Apache HTTPD documentation. Could you provide a little more > guidance on what is the difference between 'ServerName' and > 'ServerAlias'. Is there something different in the various 'ServerName' > properties of multiple VirtualHost blocks in the same HTTPD file? How > would the above VirtualHost would be preceded by Listen and|or > NameVirtualHost commands? > > TIA > Ian > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;207172674;29440083;f Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:319848 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
