Ok, so the Apache 1.3 walks/hooks flow looks like this:
----
::post read-request hook::
location_walk
- checks r->uri and sets server-wide config
::uri->filename translation hook::
directory_walk
- checks fullpath r->filename and sets per-dir config
file_walk
- checks file part of r->filename
location_walk
- second call (in case something changed)
::header parser hook::
::check access hook::
::check user id hook::
::check auth hook::
::type check hook::
::fixup hook::
::content handler hook::
::logger hook::
----
Could someone more intimate with the 2.0 code post a similar flow for 2.0?
I am just trying to make sure that this code I am writing for 1.3 right
now won't have to be completely redesigned for 2.0.
-Rasmus
On Tue, 4 Sep 2001, William A. Rowe, Jr. wrote:
> 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
> > >
> >
> >
>
