On Wednesday 12 September 2001 07:26 pm, William A. Rowe, Jr. wrote:
> From: "William A. Rowe, Jr." <[EMAIL PROTECTED]>
> Sent: Wednesday, September 12, 2001 9:22 PM
>
> > From: "Ryan Bloom" <[EMAIL PROTECTED]>
> > Sent: Wednesday, September 12, 2001 7:02 PM
> >
> > > Both. Directories and locations are equivalent. The only difference
> > > between the two containers, is that one maps to a location on the file
> > > system, and the other doesn't.
> >
> > You are out of your mind
>
> [sorry, wrong alt key]
>
> ... if you confuse <Location /> (the root of the web server's URI space)
> with <Directory /> (the root of the filesystem.)
>
> They are cousins, but they do entirely different things. This has always
> been so.
>
> Try in 1.3...
>
> DocumentRoot /www/pages
> <Directory /www/pages>
> order allow,deny
> allow from all
> </Directory>
> <Location />
> order deny,allow
> deny from all
> </Location>
>
> What do you observe?
Read it again Will. I did NOT say that
<Directory /> is equivalent to <Location />
I said that <Directory> and <Location> are equivalent operations.
When I set the DocumentRoot to /usr/local/apache/htdocs, then every
URI that does not map to the disk can effectively be treated as residing
under /usr/local/apache/htdocs.
This way, I can set Options at root of the filesystem, and it still applies
for all the URIs. If I do the following:
DocumentRoot /usr/local/apache/htdocs
<directory /usr/local/apache/htdocs>
Options ALL
</directory>
That should be equivalent to
<Location />
Options ALL
</Location>
by doing the DocumentRoot, I have set up a relationship between the URI /
and the directory /usr/local/apache/htdocs. I am just asking that the relationship
be honored.
And please don't tell me I am out of my mind. :-)
Ryan
______________________________________________________________
Ryan Bloom [EMAIL PROTECTED]
Covalent Technologies [EMAIL PROTECTED]
--------------------------------------------------------------
