On 9/20/2010 11:12 AM, William A. Rowe Jr. wrote: > On 9/18/2010 5:45 PM, Stefan Fritsch wrote: >> >> What do other people think about removing <Limit> and <LimitExcept> >> and adding mod_allowmethods from the sandbox to easily forbid some >> methods? Or would this create too much trouble when upgrading >> configurations? > > The unfinished bit of that patch is deciding how and where the section > merge will occur. Since it's a NTP that could lead to some degree of > confusion about scoping, it really seems like that should happen every > time a per-dir merge occurs. > > What I'm thinking of for the solution is to have a post-merge hook, so > that remerges can occur for any registered section provider. The whole > <Files > merge could become one consumer of this hook. That hook would, > of course, return a newly merged section or the identity of the source > dir config, if everyone declines. It's recursive, in that you could > end up with a nested Files in a location, which in turn has nested methods > which are acceptable. > > Does anyone have thoughts on the best way to handle per-dir nesting?
I think perhaps the best solution is a sandbox where we could collaborate on the unfinished aspect of this patch, and abuse the proxy/location/dir/files handlers into cooperating with a new schema. If noone objects, I'll fork the sandbox for this experiment later this evening.
