On Mon, 9 Dec 2013 14:02:33 -0500 Jim Jagielski <[email protected]> wrote:
> We know that ProxyPass works in <Location>, since it was > added in http://svn.apache.org/viewvc?view=revision&revision=1026184. > > However, the very next patch > (http://svn.apache.org/viewvc?view=revision&revision=1031758) > prevents it from working in <Directory> (as well as <Files>, but I'm > ignoring that)... > > My question is why? From what I can see, the only reason > is to close https://issues.apache.org/bugzilla/show_bug.cgi?id=47765 > but I again wonder why we allow Location but not Directory? > > Anyone have any further info on why? And yes, this is related > to https://issues.apache.org/bugzilla/show_bug.cgi?id=54965 Just one quick observation; on case insensitive file systems, we correct /mixedcase/ (the directory name) to /docroot/MixedCase/ - how this would then interact with the proxied user URL becomes an interesting question. I would argue they don't interact because <files > and <directory > should not be in the 'core of cores', but a separate loadable content provider module. We know we aren't there right now (and have discussed this before). But over a long history, people misused <Location > when they desired directory-level acls, and this encourages <Directory > and <Files > to be similarly confused. That said, I'm -0 on mixing these concepts, but if you can invent a use case for <Directory > you can just as easily invent a use case for <Files >.
