From: "Bill Stoddard" <[EMAIL PROTECTED]>
Sent: Tuesday, September 04, 2001 8:24 AM
> directory_walk, file_walk and the second call to location_walk occur after the
> translate_name hook. Last time I looked, this was still the case in 2.0.x. So, config
> directives accessed by the translation hook can only be server wide.
Right. The initial Location walk is inescapable. In the translate_name hook, the
module may modify the virtual host, the uri, assign a filename, etc.
If the module doesn't handle a filesystem resource (a la server_info or server_status)
you may skip the directory_walk and file_walk in the new map_to_storage hook. You may
even substitute your own rasmus_walk :) But when all is said and done, the system
_remerges_ the location_walk, overlaying it on top of your per_dir_configs, if the
map_to_storage handler changes the per_dir_config. If the URI is modified, it even
goes so far as to rewalk the URI before merging it.
Essentially, a module author cannot circumvent what the Administrator specifies
in the <Location > directives. And that, I believe, is goodness.
> > Are per-dir configs available before the uri->filename translation handler
> > in 1.3.x, or do they apply to the translated filenames and thus any config
> > directives accessed by the filename translation hook can only be
> > server-wide?
> >
> > And is this the same in 2.0.x?
> >
> > It would make sense to me for this to be the case, but I am just looking
> > for a sanity check here to verify what I am seeing in my code.
> >
> > -Rasmus
> >
>
>
