>>or wathever. Killing AuthtType is good in that it propably lets you >>combine different Accesses with Auth much cleaner. >> >>Dw > > > Good point. After thinking about it, it seems that AuthType could be > eliminated completely. The authentication type is already implied by > the use of the directives AuthBasicProvider, AuthDigestProvider or any > other AuthXXXProvider that may come along in the future. Does anybody > see a need to keep AuthType around at all under the new authentication > architecture?
I'm going a few rounds at the moment with a user that's confused between ap_auth_type(r) and r->ap_auth_type, and why ap_auth_type(r) needs to be set at all if he's writing his own non-basic-non-digest authentication scheme. making the authtype indigenous to the provider mechanisms make a decent amount of sense to me. --Geoff
