https://bz.apache.org/bugzilla/show_bug.cgi?id=70025

Philippe Cloutier <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |NEW

--- Comment #2 from Philippe Cloutier <[email protected]> ---
(In reply to Rich Bowen from comment #1)
> So, if I am understanding this, your concern is that this document suggests
> that it's set to All by default, when it is in fact set to None, yes?
Basically
More exactly, that section implies that the FollowSymLinks and/or
SymLinksIfOwnerMatch option:
1. is enabled by default
2. is only disabled with “AllowOverride None” (while in fact, AllowOverride
Options=None and multiple other values can cause that).

> Meanwhile, we frequently see in the wild instances where people have gone
> into the main config and set it to All for <Directory /> "for convenience",
> and that's what this is cautioning against.
> 
> Could you perhaps suggest phrasing that covers both eventualities?
The current phrasing is ambiguous, but assuming I am understanding right:

> While processing a request, in every directory of the path to the resource 
> for which distributed configuration files are enabled, the server looks for 
> the first existing configuration file from this list of names. For example, 
> if distributed configuration files are enabled everywhere, with the following 
> directive, before returning the document /usr/local/web/index.html, the 
> server will process the directives in /.acl, /usr/.acl, /usr/local/.acl and 
> /usr/local/web/.acl:
> AccessFileName .acl

> The goal of the documentation is to promote best practice, and this comment 
> in the
> doc is to make people aware of the cost of setting this directive to
> something other than the default value.
I am sorry, but if that's the goal, I had not understood that, and I still do
not understand that at all after a new careful read.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to