The following reply was made to PR other/212; it has been noted by GNATS.

From: [EMAIL PROTECTED] (James R Grinter)
To: Marc Slemko <[EMAIL PROTECTED]>, Rodent of Unusual Size <[EMAIL PROTECTED]>
Subject: Re: other/212: name resolution of vhosts
Date: Sat, 1 Mar 1997 12:45:18 +0000

 
 On Sat 1 Mar, 1997, Marc Slemko <[EMAIL PROTECTED]> wrote:
 >On Fri, 28 Feb 1997, Rodent of Unusual Size wrote:
 >>  This has also been reported as PR#105 in the Apache bug
 >>  database.
 >
 >Not really.  That was about it not starting and saying it should skip
 >them; that is a valid request.  This one is mostly saying Apache doesn't
 
 pr#150 is talking about forward resolution of virtualhost declarations
 (probably why i didn't find it in a search before submitting). His
 suggestion is to ignore that declaration and log it in error_log.
 
 my pr is about reverse lookups. The bit of code I quoted makes
 apache lookup the forward name for the ip address: this seemed
 like a bad idea to me.
 
 >need the hostname, which is entirely false; HTTP/1.1 and non-IP virtual
 >hosts require that Apache know the hostname.  As I told the user on
 >c.i.w.s.u, if you don't want Apache to insist on reverse DNS use a
 >ServerName directive to tell it what to use.
 
 hm, you're saying that it won't enter that bit of code if I put
 a ServerName directive? But that certainly isn't obvious, and as
 I was experimenting with the <virtualhost 255.255.255.255> default
 thing, a servername doesn't seem like something one needs.
 
 >Haven't had time to look at what is being said about the logging yet.  On
 >the surface, this just looks to be a feature request; I am unsure about if
 >that is a good idea because it obscures what configured virutal domain a
 >request was for, but may be ok as a seperate variable.  
 
 That's what I shall do, for myself. (I'm actually trying to genericise
 things, as holding many VirtualHost config entries and searching
 through them when they're all practically identical doesn't seem)
 
 It sounds like a good fix for the situation of no reverse dns lookup
 would be to change the error message to suggest adding a ServerName
 directive.
 
 -- jrg.

Reply via email to