I'm with Joshua. I don't see the need/purpose for creating a second
mechanism for aliasing locations to filesystem paths. Why have two? Why have
to answer "which should I use?" etc etc
Cheers,
-g
On Mon, Sep 10, 2001 at 11:48:57AM -0400, Joshua Slive wrote:
>
> > + * Allow the DocumentRoot directive within <Location > scopes? This
> > + allows the beloved (crusty) Alias /foo/ /somepath/foo/ followed
> > + by a <Directory /somepath/foo> to become simply
> > + <Location /foo/> DocumentRoot /somefile/foo (IMHO a bit more
> legible
> > + and in-your-face.) This proposed change would not depricate
> Alias.
>
> I don't like that. (Sorry to be a constant nay-sayer on config changes ;-)
>
> 1. It overloads DocumentRoot. "Root" should mean "/".
>
> 2. It encourages people to use <Location> where they should be using
> <Directory>.
> (Imagine if you protected this <Location> block with basic auth, but forgot
> that another URL can access the same directory.)
>
> If you wanted to add a "URLMapTo" directive that does something similar, I
> would be less opposed. But I still would not be in favour.
>
> Joshua.
--
Greg Stein, http://www.lyra.org/
