On 12 Jul 2019, at 02:51, Eric Covener <cove...@gmail.com> wrote: > Because the last thing merged into authz_cores r->per_dir_config is a > dirconf w/ `require valid-user` directives from the if/else. > > What else could it mean for <If> to be merged last?
For a start it means that this part of our manual is invalidated the moment you add an If statement: http://httpd.apache.org/docs/current/sections.html >> Most specifically, why does “require all denied” have no effect when a file >> matches that directory section? > > Because the core added an <If> section and is going to evaluate it > later. Even if you used some core directives inside the 2nd > <Directory> section to cause a merge to happen, there is no directive > that removes/resets existing <If> sections from cores per-dir-config. > They are accumulated in the early configuration section walking then > evaluated after. I am trying to get my head around how we can make If work like the docs above. Is If broken, or is require broken? Regards, Graham —
smime.p7s
Description: S/MIME cryptographic signature