[Bug 70025] AccessFileName Directive: Outdated regarding AllowOverride

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

--- Comment #4 from Philippe Cloutier <[email protected]> ---
Thank you Rich

Your change solves the case which I reported, but I am concerned the addition
about the default stanza introduces a similar issue. I asked about that in the
GitHub’s page for the commit.

(In reply to Rich Bowen from comment #3)
> Also removed the example of setting AccessFileName to a non-standard value.
> Documentation should not only describe functionality but also recommend best
> practice — suggesting that people rename their distributed configuration
> files serves no purpose other than making troubleshooting harder for
> everyone involved.
I agree that documentation can describe best practice, but I do not understand
the example as a suggestion. Examples illustrate descriptions, and I for one
pretty much believe every non-trivial (boolean) setting should have an example,
unless perhaps the setting is dangerous/deprecated. httpd documentation
contains completely fabricated examples which are not suggestions at all.

I can see reasons to use AccessFileName, in particular the unclear default and
the lack of l10n.

-- 
You are receiving this mail because:
You are the assignee for the bug.