after gathering pages of scribbles from comparing 2.2.x/modules<->2.3.x/modules and 2.2.x/include<->2.3.x/include for API changes and trying to describe as many as I could, I'm left with a list of things to research further:
check_user_id->check_authn access_checker->check_access auth_checker->check_authz AUTHN_PROVIDER_VERSION? note_basic_auth_failure ap_register_provider->ap_register_auth_provider ap_authn_cache_store ap_hook_auth_checker->register_auth_provider access_checker_ex What's the big picture here? Is it something like IF YOU USE THE UGLY LEGACY HTTPD 1.3/2.0 MODEL: * dudette, your code still works (but shame on you for not using the 2.2 provider framework) * you may be interested in switching to the 2.4 provider framework, which allows for XXX,YYY,ZZZ * you may be interested in these new features: AAA,BBB,CCC If you use the httpd 2.2 provider framework (ponies and rainbows): * change1 (e.g., "0"->AUTHN_PROVIDER_VERSION) * change2 * ... * changen * you may be interested in these new features: AAA,BBB,CCC hints?
