Bill Stoddard wrote: >> mod_status and mod_info both are enabled via <Location > containers. >> mod_status never DECLINEs if it is the handler. mod_info DECLINEs if >> the method isn't GET. Let me see what happens if I send mod_info some >> other method. > > > My not so well formed thoughts are that if a module claims it should > handle a request based on a SetHandler directive in a Location > directive, the server should not allow that handler to DECLINE the > request. Putting it another way, if the handler claims the request then > DECLINEs, the server should prevent other handlers from attempting to > serve the request.
I've brought this up before, but if you shortcut translation, how do you handle cases where r->handler is set after translation/map_to_storage. that is, just because at the start of a request <Location /foo> refers to a non-static resource, doesn't mean that assumption won't change. see mod_dav and mod_include, both of which set r->handler during the fixup phase. [EMAIL PROTECTED] wrote: > A map_to_storage hook needs to know when to allow the directory walk and > when not to. I think I see what you mean. so, perhaps the answer to my question above is that, with your patch, if modules expect to set r->handler under certain conditions, then they ought to install their own map_to_storage handler to handle those conditions as well? --Geoff
