On Saturday 22 December 2012, Eric Covener wrote: > Currently, AuthMerging is unset by default and treated as off. > This flag is itself not merged. > > The default behavior matches the pre-2.4 behavior -- once you > start typing any kind of host or authz directives in a section, > you have a clean slate. > > I was thinking it would be useful if AuthMerging itself was merged > traditionally, such that e.g. this config: > > <Files *.bak> > AuthMerging AND > Require all denied > Require ip 127.0.0.1 > </Files> > > ... 1000 lines of other unrelated directives > > # contrived bad and unnecessary regex > <FilesMatch html> > Require all granted > </Files> > > Would merge AuthMerging AND into the second section -- basically > making the first section "sticky" from below instead of pulling it > in from above. > > Thoughts?
I have not thought it completely through, but I suspect this would have rather surprising effects with "AuthMerging OR". Would an optional second parameter to AuthMerging be better? Like <Files *.bak> AuthMerging AND inherit Require all denied Require ip 127.0.0.1 </Files>
