Ryan Bloom wrote: > > On Sunday 23 December 2001 06:27 am, Jeff Trawick wrote: > > Greg Ames <[EMAIL PROTECTED]> writes: > > > > > ...are more painful to deal with than you might think, if the user is > > > allowed to code them in any order. > > > > another thing is that the user can code any number of them, possibly > > with different values... swapping items in the tree doesn't > > necessarily deal with that properly while doing stuff in a post-config > > hook wouldn't run into problems (it could just use the setting from > > the last time the directive occurred) > > The problem with doing it in post-config is that it isn't generic > enough. It will work for any directive that is only allowed in the main server > config, but you can't really use it for anything in a different scope.
You're right. Good point. > Since > we already know that we need this general ability for some of the auth > directives (see John Sterling's posts about some of the problems with AuthType > and AuthName), I would much rather have a generic function that will > manipulate the tree itself. Swapping things in the config tree breaks if the nodes involved are in different scopes: AuthType basic <Directory /docroot/flintstone > AuthName Fred </Directory > <Directory /docroot/rubble > AuthName Barney </Directory > I think that's a legitimate config. But if we swapped AuthName & AuthType, we would destroy it. Greg
