On Thu, Sep 13, 2001 at 12:24:03PM -0400, Joshua Slive wrote:
> > -----Original Message-----
> > From: Ian Holsman [mailto:[EMAIL PROTECTED]]
> > What I am suggesting is to move some of these configurations to
> > <Location /> where they belong.
>
> I don't see any config directives that "belong" in <Location />.
> Please be more specific before you do anything.
Options Indexes
AllowOverride None
Order allow,deny
Allow from all
AddHandler type-map var
DirectoryIndex index.html index.html.var
The only thing that is filesystem specific are:
Options FollowSymLinks
> > (BTW.. there are NO '<location>' directives installed in the
> > httpd-std.conf)
>
> There are commented out location directives for /server-status and
> /server-info
>
> In general, I think this is proper. Most people serve content from the
> filesystem. When serving content from the filesystem, <directory> should be
> used in preference to <location> for the reasons I mentioned a couple days
> ago in another thread. We should not be encouraging people to use
> <location> except in specific circumstances.
<Location /> is different. It is setting global configuration for the whole
server. It ensures that you don't miss some critical bits.
And your cut/dry "Directory good. Location bad." does not hold. All of my
configurations are Location based. That is because accessing the content
through one location gives you DAV capabilities, and the other location
gives your PHP- or SSI-processed content.
With Subversion, we *only* have Location directives. There is absolutely
nothing on the disk to serve.
<Location> is an important directive and needs to be used in many, many
cases.
In this particular case, the problem arose because the attempt to set
"global" options broke down. It was set only for one directory, not the
whole server URL space. Using <Location /> fixes that.
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
