On 12 Jul 2019, at 01:32, Eric Covener <cove...@gmail.com> wrote: >> My understanding is that we walk first to last, and the last matching >> configuration wins, and in theory that means the LocationMatch should win. > The last match doesn't win, it's merged on top of whatever the current > per-dir*per-module config is.
That’s what I mean by “win” - it takes precedence and is merged on top of earlier config. > Just like a normal mod, whoever evaluates <if> (core) can decide to > replace/merge/append then act on that config later. > The merge for If sections encountered is to accumulate them in the > per-dir config. After all the other sections have been parsed, the > accumulated if sections are evaluated shortly after the traditional > location/dirwalk stuff. > > sections.html does show <if> as evaluated last: > http://httpd.apache.org/docs/current/sections.html#merging I know that Ifs are evaluated last, but what concrete effect does this have? Or to put it another way, what changes do I need to make to the earlier config to “punch a hole” in the URL space such that “…/unsubscribe” is always granted access? I am having the exact same problem with Directory and DirectoryMatch. When there are Ifs in a Directory, the Directory overrides the DirectoryMatch, even though the DirectoryMatch is more specific and should “win” (win meaning be merged on top of all that has gone before it). Regards, Graham —
smime.p7s
Description: S/MIME cryptographic signature
