This module provides authentication front-ends such as
    
This module relies on 
When using dbd value.
Some users of DBD authentication in HTTPD 2.2 have reported that it
imposes a problematic load on the database.  This is most likely where
an HTML page contains hundreds of objects (e.g. images, scripts, etc)
each of which requires authentication.  Users affected (or concerned)
by this kind of problem should use 
This simple example shows use of this module in the context of the Authentication and DBD frameworks.
If httpd was built against 
If a database query for example returned the username, full name and telephone number of a user, a CGI program will have access to this information without the need to make a second independent database query to gather this additional information.
This has the potential to dramatically simplify the coding and configuration required in some web applications.
The %s format specifier.
The first column value of the first row returned by the query
    statement should be a string containing the encrypted password.
    Subsequent rows will be ignored.  If no rows are returned, the user
    will not be authenticated through 
If httpd was built against AUTHENTICATE_COLUMN.
    
The encrypted password format depends on which authentication
    frontend (e.g. 
The %s format specifiers.
The first column value of the first row returned by the query
    statement should be a string containing the encrypted password.
    Subsequent rows will be ignored.  If no rows are returned, the user
    will not be authenticated through 
If httpd was built against AUTHENTICATE_COLUMN.
    
The encrypted password format depends on which authentication
    frontend (e.g.