Is there really a rationale for that name change?
This module is *not* an authz module in the sense of anything from
the used-to-be-auth modules are.
* It lives on a different request processing hook.
* Its semantics, and even HTTP failure code, are different.
* it uses TCP information rather than HTTP information.
* It has a clear but *distinct* relationship with the real authz,
expressed in the Satisfy Any|All directive.
Reverting the name to mod_access will make it immediately more
accessible to users (a name they know), and reduce the scope
for future confusion. How about it?
--
Nick Kew
