Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Sender: cturner@redhat.com
To: dev@httpd.apache.org
Subject: Re: Directory completion?
References: <1009841782.17264.6.camel@UberGeek>
	<20011231155336.X1529@clove.org> <07ab01c19258$aa4f36e0$95c0b0d0@v505>
From: Chip Turner <cturner@redhat.com>
Date: 31 Dec 2001 22:27:45 -0500
In-Reply-To: <07ab01c19258$aa4f36e0$95c0b0d0@v505>
Message-ID: <vzkbsgevjgu.fsf@minbar.devel.redhat.com>
Lines: 33
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

"William A. Rowe, Jr." <wrowe@covalent.net> writes:

> > On Mon, Dec 31, 2001 at 05:36:22PM -0600, Austin Gonyou wrote:
> > > If I add a directory to my httpd.conf and restart apache, or I add a
> > > directory to htdocs, then point my browser as such:
> > > 
> > > http://127.0.0.1/somedir
> > > 
> > > It hangs until the browser times out. If I do the following though,
> > > without restarting apache, etc:
> > 
> > My guess is your ServerName is set to something that doesn't exist from
> > the perspective of your browser. When you request http://127.0.0.1/somedir
> > it generates a 301 Moved Permanently to whatever was in your ServerName
> > (plus the path and some other stuff), at which point your browser tries
> > to resolve that new host. If it cannot it will hang until timeout.
> 
> Yes... definately the problem [it bit me just today.]
> 
> What would the group think about validating that the ServerName/ServerAlias
> directives resolve to a valid Listen'er of this server?

Why not base the redirect on the incoming Host: header?  That should
work in most cases (certainly for the browser, also should work for
proxies in front).  This way users don't mysteriously hop servers and
such.  In cases where there is no Host, perhaps fallback to the vhost
ServerName.

Chip

-- 
Chip Turner                   cturner@redhat.com
                              Red Hat Network