Astrid Keßler wrote: >>I was just asked again by a user about the load order of modules. >>While it seems that it is now with Apache2 less important, and also >>ClearModuleList and AddModule are removed now with Apache2, I think it >>is at least still important for auth modules. So I searched the manual >>for any hints, specially about the fact that the last module loaded is >>the first module in the auth chain > > > This is true for 1.3, but not for 2.0. For 2.0 the module order of the > auth modules is undefined. They all register with the same priority at > the same hook(s). The sort is done with qsort, which does not guaranty a > stable ordering. It can differ from build to build, from libc to libc > and from httpd.conf to httpd.conf. This is a real problem if you want to > use the Auth*Authoritative directives. This problem has been solved in > the 2.1 source tree by introducing the provider mechanism for auth > modules.
Perhaps my memory is failing me, but I thought the module hooks were sorted with a stable topological sort, not qsort? Cheers, Ben. -- http://www.apache-ssl.org/ben.html http://www.thebunker.net/ "There is no limit to what a man can do or how far he can go if he doesn't mind who gets the credit." - Robert Woodruff
