httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From D Kelmi <>
Subject Re[6]: [users@httpd] NameVirtualHost * with <VirtualHost IP>
Date Fri, 05 Dec 2003 13:21:50 GMT
Hello Boyle,

Friday, December 5, 2003, 3:21:09 PM, you wrote:

>> -----Original Message-----
>> From: D Kelmi []
>>   NameVirtualHost also can take * as argument for match all addresses.

BO> Agreed - I never said it couldn't. I was correcting an earlier response
BO> by another poster who recommended putting a FQDN as an argument to
BO> NameVirtualHost.

>> BO> IP-based VHs supersede name-based VHs so the apache 
>> behaviour you see is
>> BO> exactly correct. Not a bug. 
>>    Why? I say in NameVirtualHost what my all IP addresses must support
>>    name-based virtual hosting. And now Apache must look all VHs with
>>    the same IP (same with request destination) and also look VHs with
>>    * (VHs which support any request destination). Right?

BO> Wrong. As soon as you define an IP-based VH, it will serve all requests
BO> to that IP. Hostname will be ignored. This is what I mean by "IP-based
BO> VHs supersede name-based VHs".

      Where you find something about IP-based VHs?
      I'm use NameVirtualHost directive.
      "With the NameVirtualHost directive you specify the IP address on which
      the server will receive requests for the name-based virtual hosts."
      Now, "NameVirtualHost *" say, what all IP addresses, listening
      by apache will be name-based.

BO> If you ask "why?", it's because that's the only way it makes logical
BO> sense. It's the only way you can decide the VH in a logically consistent
BO> way.

BO> Perhaps, rather than arguing about what you think *should* happen, you
BO> should explain exactly what you are trying to achieve. I am still not
BO> clear what your goal is. Please explain:

BO> - how many IP addresses do you have?
BO> - how many hosts on each IP?
BO> - how do you want to define the hosts (name or IP)?

  Big thanks, but I'm not need suggestions for setup apache - use it
  about six year :)
  But what i want to do:
     Apache listen more than one IP (now it's 2 IP, but it can be 8,
     16... or full C-class net)
     All IP's setup for name-based hosting (NameVirtualHost *)
     All domains assigned to one's IP (<VirtualHost>)
     How many domains hosted for each IP - to be of no importance.
     (!)I want to have one "dummy" VHs for each IP. If i remove some
     domains from config, this dummy site will be answer for requests
     for removed VHs and say "this domain not supported" or something
  Look down for ideal config for this.

>> Ok. Now say, which VHs will be "dummy" in this example:
>> NameVirtualHost
>> <VH *>
>>   ServerName site1
>> </VH>
>> <VH>
>>   ServerName site2
>> </VH>
>> Which? site1 or site2? I think, what site1, because <VH *> match
>> IP also. Apache think, what site2.

BO> I'm not so sure - your example is bit made-up so it's not obvious. I
BO> rather suspect that <VH *> won't match anything at all so that site2
BO> will become the default. The point is that as soon as you specify an IP
BO> with a VH, that IP leaves the wildcard list. Remember that the
BO> httpd.conf file isn't Perl or Unix - it is parsed by a custom built
BO> program and so its rules are not always what you'd expect...

   Yes, but if it's feature, not a bug - it's must be in
   About priority with <Directory path> and <Directory ~ regexp> all
   written a long time ago. If <VirtualHost ip/domain> has a lower
   priority, than <VirtualHost *>, write it.
   Now i looking httpd -S - apache at first look IP's, and only then -
   What a pity. Now i must or write dummy VHs for each listening IP,
   or write all VHs as wildcards. First choice is very overfill my
   config (when i use more ip)... in second choice not good, what one
   VHs can answer on all IP's.

BO> Rgds,
BO> Owen Boyle
BO> Disclaimer: Any disclaimer attached to this message may be ignored.

>> -- 
>> Best regards,
>>  D Kelmi               
BO> Diese E-mail ist eine private und persönliche Kommunikation. Sie hat
BO> keinen Bezug zur Börsen- bzw. Geschäftstätigkeit der SWX Gruppe. This
BO> e-mail is of a private and personal nature. It is not related to the
BO> exchange or business activities of the SWX Group. Le présent e-mail est
BO> un message privé et personnel, sans rapport avec l'activité boursière du
BO> Groupe SWX.

BO> This message is for the named person's use only. It may contain
BO> confidential, proprietary or legally privileged information. No
BO> confidentiality or privilege is waived or lost by any mistransmission.
BO> If you receive this message in error, please notify the sender urgently
BO> and then immediately delete the message and any copies of it from your
BO> system. Please also immediately destroy any hardcopies of the message.
BO> You must not, directly or indirectly, use, disclose, distribute, print,
BO> or copy any part of this message if you are not the intended recipient.
BO> The sender's company reserves the right to monitor all e-mail
BO> communications through their networks. Any views expressed in this
BO> message are those of the individual sender, except where the message
BO> states otherwise and the sender is authorised to state them to be the
BO> views of the sender's company. 

Best regards,

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message