almost never be used except on tightly controlled internal
networks. Apache httpd will not even attempt to determine
this information unless <directive
- module="core">IdentityCheck</directive> is set
+ module="mod_ident">IdentityCheck</directive> is set
to <code>On</code>.</dd>
<dt><code>frank</code> (<code>%u</code>)</dt>
<p>In typical operation, Apache is started by the root user, and it
switches to the user defined by the <directive
- module="mpm_common">User</directive> directive to serve hits. As is the
+ module="mod_unixd">User</directive> directive to serve hits. As is the
case with any command that root executes, you must take care that it is
protected from modification by non-root users. Not only must the files
themselves be writeable only by root, but so must the directories, and
<p>Embedded scripting options which run as part of the server itself,
such as <code>mod_php</code>, <code>mod_perl</code>, <code>mod_tcl</code>,
and <code>mod_python</code>, run under the identity of the server itself
- (see the <directive module="mpm_common">User</directive> directive), and
+ (see the <directive module="mod_unixd">User</directive> directive), and
therefore scripts executed by these engines potentially can access anything
the server user can. Some scripting engines may provide restrictions, but
it is better to be safe and assume not.</p>
<p> If a connection is not successful with the timeout period, either an error will be
returned or the LDAP client library will attempt to connect to a secondary LDAP
server if one is specified (via a space-separated list of hostnames in the
- <directive module="mod_ldap">AuthLDAPURL</directive>).</p>
+ <directive module="mod_authnz_ldap">AuthLDAPURL</directive>).</p>
<p>The default is 10 seconds, if the LDAP client library linked with the
server supports the LDAP_OPT_NETWORK_TIMEOUT option.</p>
projects / apache / commitdiff