Chip,
You've just described an existing directive;
With UseCanonicalName off Apache will form
self-referential URLs using the hostname and port supplied by
the client if any are supplied (otherwise it will use the
canonical name). These values are the same that are used to
implement name based virtual hosts, and are available with the
same clients. The CGI variables SERVER_NAME and SERVER_PORT
will be constructed from the client supplied values as well.
----- Original Message -----
From: "Chip Turner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, December 31, 2001 9:27 PM
Subject: Re: Directory completion?
> "William A. Rowe, Jr." <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED]
> Red Hat Network
>
