httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Reid" <dr...@jetnet.co.uk>
Subject Re: confused about new ServerName logic
Date Wed, 21 Jun 2000 19:14:18 GMT
I'm with Jeff on this one.  Convince me otherwise.

david

> > 
> > > > Your {} block is entirely wrong.  You will only display 
> > > messages if we
> > > > 'assume' a localhost ip?  What about the fool with 15 dns 
> > > aliases who
> > > > can't understand why their server responds with the name 
> > > pigsfeet.ugh,
> > > > and can't seem to change it (no idea why...)
> > > 
> > > I don't think it is so nice to issue an error message on the console
> > > for a situation we do not know to be in error and which has been
> > > happily accepted by Apache with no complaints for a long period of
> > > time.  If we have to assume 127.0.0.1, yes that is a configuration
> > > almost definitely in error and it should be an error message on the
> > > console like you have it.  If gethostname() and gethostbyname()
> > > worked, however, then I don't think we should complain so loudly.  An
> > > info or warning message in the log should suffice.  I would *guess*
> > > that there are great numbers of existing apache installations with no
> > > ServerName but a valid DNS setup and hence no problems.
> > 
> > Ok... issue one, this patch was already accepted into 1.3.13, and 2.0
> > is a new beast, so we don't have to follow the 'it worked this way
> > before' arguments if we are improving the product.  But on to the
> > Q...
> 
> Strictly speaking, there is no 1.3.13, only 1.3.13-dev, so it is fair
> to say that it didn't work this way before.  
> 
> Perhaps I'm the only one that feels this way, but on several of my
> machines I have no ServerName and I see no reason to add it and I
> don't think I need an error message on the terminal that won't go away
> until I add it.  I could accept it as an informational message in the
> log, but an error message tells me I need to go do something now, and
> I don't think that is appropriate in my case.
> 
> What about an error message on the terminal if gethostname() fails or
> gethostbyname() fails or find_fqdn() fails, and either no message or
> an informational message in the log otherwise?
> 
> > We document in httpd.conf that they should fill this in.  Providing a
> > warning that they haven't isn't bad, IMHO.
> 
> I don't interpret the prose in http.conf as saying that users "should"
> fill this in.  The documentation of the ServerName directive and
> linked documentation on DNS issues is stronger, but I think it is
> mostly a description of the conditions in which you should set it.
> 
> Have fun,
> 
> -- 
> Jeff Trawick | trawick@ibm.net | PGP public key at web site:
>      http://www.geocities.com/SiliconValley/Park/9289/
>           Born in Roswell... married an alien...
> 


Mime
View raw message