On Fri, Jul 23, 2010 at 11:14 AM, Jeff Trawick <traw...@gmail.com> wrote: > On Sun, Jul 11, 2010 at 11:28 AM, <n...@apache.org> wrote: >> Author: niq >> Date: Sun Jul 11 05:58:13 2010 >> New Revision: 962989 >> >> URL: http://svn.apache.org/viewvc?rev=962989&view=rev >> Log: >> Backport FallbackResource directive. >> > ... >> Modified: httpd/httpd/branches/2.2.x/modules/mappers/mod_dir.c >> URL: >> http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/modules/mappers/mod_dir.c?rev=962989&r1=962988&r2=962989&view=diff >> ============================================================================== >> --- httpd/httpd/branches/2.2.x/modules/mappers/mod_dir.c (original) >> +++ httpd/httpd/branches/2.2.x/modules/mappers/mod_dir.c Sun Jul 11 05:58:13 >> 2010 > ... >> @@ -243,6 +291,7 @@ static int fixup_dir(request_rec *r) >> static void register_hooks(apr_pool_t *p) >> { >> ap_hook_fixups(fixup_dir,NULL,NULL,APR_HOOK_LAST); >> + ap_hook_fixups(fixup_dflt,NULL,NULL,APR_HOOK_LAST); > > Does anybody recall an issue with modules that have multiples of the > same hook, creating a problem for other modules that want to go > specifically before or after the module? > (I think there is an issue with hook sorting, such that > successor/predecessor doesn't work in this case.)
If a module specifies mod_dir.c as a predecessor for a fixups hook, that module's fixups hook will be placed between the two fixups hooks of mod_dir.c.
