Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
Errors-To: <wrowe@rowe-clan.net>
From: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
To: <new-httpd@apache.org>
Subject: FW: os-windows/6787: I've specified ServerName in httpd.conf and I
 can't use the name in none of my browsers
Date: Thu, 2 Nov 2000 10:03:50 -0600
Message-ID: <006e01c044e6$7dc62b80$92c0b0d0@roweclan.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Importance: Normal

Folks,

  does anyone have an extra 1/2 hour of their life to add DNS validation
parsing to the ServerName argument, so we return an intellegent message
before we start the server and fail to fill requests to bad DNS names?
I don't have my fingers over there right now, and this may become a more
common error report in the future that Joshua, Tony and I don't want to
keep debugging/answering.  I've added a showstopper on it, since that DNS
hostname patch added more work for the group than it has eliminated.

Bill

> From: William A. Rowe, Jr. [mailto:wrowe@rowe-clan.net] 
> Sent: Thursday, November 02, 2000 9:32 AM
> To: apache-bugdb@apache.org; peti@aiinformatics.ro
> Subject: Re: os-windows/6787: I've specified ServerName in httpd.conf
> and I can't use the name in none of my browsers
> 
> > From: Zsehranszky Peter [mailto:peter.zsehranszky@aiinformatics.ro] 
> > Sent: Thursday, November 02, 2000 9:47 AM
> > 
> > Thank's but: like I said I used the same (and unchanged httpd.conf for
> > both of the versions: 1.3.9 and 1.3.14) and with 1.3.9 works and with
> > 1.3.14 doesn't works. Anyway, in error.log I found something like this
> > when I used 1.3.14 and I tried to open the mainpage using the name
> > specified in ServerName:
> > [Thu Nov 02 12:57:15 2000] [error] [client 194.173.101.61] Client sent
> > malformed Host header...
> 
> Looking at your httpd.conf, you cannot use underscores (_) in your
> ServerName ... but I agree that the error reporting is nonsense.  I'm
> leaving the report open till some parsing is added to return a decent
> error message!  Try changing your hosts file and ServerName entries to
> a valid DNS entry (use hyphens (-) instead) and see if that solves it.