core.html.en

apache 安装教程 apache 安装教程

    <p>This directive selects the type of user authentication for a
    directory. Only <code>Basic</code> and <code>Digest</code> are
    currently implemented. 

     It must be accompanied by <a href="#authname">AuthName</a> and
    <a href="#require">Require</a> directives, and directives such
    as <a href="mod_auth.html#authuserfile">AuthUserFile</a> and <a
    href="mod_auth.html#authgroupfile">AuthGroupFile</a> to
    work.</p>

    <p>When AuthDigest is used an <a href="#AuthDigestRealmSeed">AuthDigestRealmSeed</a>
    should also be set.</p>

    <p><strong>See also:</strong> <a
    href="../howto/auth.html">Authentication, Authorization, and
    Access Control</a></p>
    <hr />

    <h2><a id="bindaddress" name="bindaddress">BindAddress
    directive</a></h2>

    <a href="directive-dict.html#Syntax"
    rel="Help"><strong>Syntax:</strong></a> BindAddress
    *|<em>IP-address</em>|<em>domain-name</em><br />
     <a href="directive-dict.html#Default"
    rel="Help"><strong>Default:</strong></a> <code>BindAddress
    *</code><br />
     <a href="directive-dict.html#Context"
    rel="Help"><strong>Context:</strong></a> server config<br />
     <a href="directive-dict.html#Status"
    rel="Help"><strong>Status:</strong></a> core<br />
     <a href="directive-dict.html#Compatibility"
    rel="Help"><strong>Compatibility:</strong></a> BindAddress is
    deprecated and will be eliminated in Apache 2.0.

    <p>A Unix&reg; http server can either listen for connections to
    every IP address of the server machine, or just one IP address
    of the server machine. If the argument to this directive is *,
    then the server will listen for connections on every IP
    address. Otherwise, the server can listen to only a specific
    <em>IP-address</em> or a fully-qualified Internet
    <em>domain-name</em>.</p>

    <p>For example:</p>

    <code>BindAddress 192.168.15.48</code><br />

    <p>Only one <code>BindAddress</code> directive can be used.</p>
    
    <p>This directive is deprecated and will be eliminated in
    Apache 2.0.  Equivalent functionality and more control over the
    address and ports Apache listens to is available using the
    <code><a href="#listen">Listen</a></code>
    directive.</p>

    <p><code>BindAddress</code> can be used as an alternative
    method for supporting <a href="../vhosts/">virtual hosts</a>
    using multiple independent servers, instead of using <code><a
    href="#virtualhost">&lt;VirtualHost&gt;</a></code>
    sections.</p>

    <p><strong>See Also:</strong> <a href="../dns-caveats.html">DNS
    Issues</a><br />
     <strong>See Also:</strong> <a href="../bind.html">Setting
    which addresses and ports Apache uses</a></p>
    <hr />

    <h2><a id="bs2000account" name="bs2000account">BS2000Account
    directive</a></h2>

    <a href="directive-dict.html#Syntax"
    rel="Help"><strong>Syntax:</strong></a> BS2000Account
    <em>account</em><br />
     <a href="directive-dict.html#Default"
    rel="Help"><strong>Default:</strong></a> <em>none</em><br />
     <a href="directive-dict.html#Context"
    rel="Help"><strong>Context:</strong></a> server config<br />
     <a href="directive-dict.html#Status"
    rel="Help"><strong>Status:</strong></a> core<br />
     <a href="directive-dict.html#Compatibility"
    rel="Help"><strong>Compatibility:</strong></a> BS2000Account is
    only available for BS2000 machines, as of Apache 1.3 and later.
    

    <p>The <code>BS2000Account</code> directive is available for
    BS2000 hosts only. It must be used to define the account number
    for the non-privileged apache server user (which was configured
    using the <a href="#user">User</a> directive). This is required
    by the BS2000 POSIX subsystem (to change the underlying BS2000
    task environment by performing a sub-LOGON) to prevent CGI
    scripts from accessing resources of the privileged account
    which started the server, usually <samp>SYSROOT</samp>.<br />
     Only one <code>BS2000Account</code> directive can be used.</p>

    <p><strong>See Also:</strong> <a href="../ebcdic.html">Apache
    EBCDIC port</a></p>
    <hr />

    <h2><a id="cgicommandargs" name="cgicommandargs">CGICommandArgs
    directive</a></h2>

    <a href="directive-dict.html#Syntax"
    rel="Help"><strong>Syntax:</strong></a> CGICommandArgs On|Off<br />
     <a href="directive-dict.html#Default"
    rel="Help"><strong>Default:</strong></a> CGICommandArgs On<br />
     <a href="directive-dict.html#Context"
    rel="Help"><strong>Context:</strong></a> directory, .htaccess<br />
     <a href="directive-dict.html#Override"
    rel="Help"><strong>Override:</strong></a> Options<br />
     <a href="directive-dict.html#Status"
    rel="Help"><strong>Status:</strong></a> core<br />
     <a href="directive-dict.html#Compatibility"
    rel="Help"><strong>Compatibility:</strong></a> Available in Apache
       1.3.24 and later.

    <p>Way back when the internet was a safer, more naive place, it
    was convenient for the server to take a query string that did not
    contain an '=' sign and to parse and pass it to a CGI program as
    command line args.  For example, <code>&lt;IsIndex&gt;</code>
    generated searches often work in this way.  The default behavior
    in Apache is to maintain this behavior for backwards
    compatibility, although it is generally regarded as unsafe
    practice today.  Most CGI programs do not take command line
    parameters, but among those that do, many are unaware of this
    method of passing arguments and are therefore vulnerable to
    malicious clients passing unsafe material in this way. Setting
    <code>CGICommandArgs Off</code> is recommended to protect such
    scripts with little loss in functionality.</p>

    <hr />

    <h2><a id="clearmodulelist"
    name="clearmodulelist">ClearModuleList directive</a></h2>

    <a href="directive-dict.html#Syntax"
    rel="Help"><strong>Syntax:</strong></a> ClearModuleList<br />
     <a href="directive-dict.html#Context"
    rel="Help"><strong>Context:</strong></a> server config<br />
     <a href="directive-dict.html#Status"
    rel="Help"><strong>Status:</strong></a> core<br />
     <a href="directive-dict.html#Compatibility"
    rel="Help"><strong>Compatibility:</strong></a> ClearModuleList
    is only available in Apache 1.2 and later 

    <p>The server comes with a built-in list of active modules.
    This directive clears the list. It is assumed that the list
    will then be re-populated using the <a
    href="#addmodule">AddModule</a> directive.</p>

    <p><strong>See also</strong>: <a
    href="#addmodule">AddModule</a> and <a
    href="mod_so.html#loadmodule">LoadModule</a></p>
 
    <hr />

    <h2><a id="contentdigest" name="contentdigest">ContentDigest
    directive</a></h2>

    <a href="directive-dict.html#Syntax"
    rel="Help"><strong>Syntax:</strong></a> ContentDigest
    on|off<br />
     <a href="directive-dict.html#Default"
    rel="Help"><strong>Default:</strong></a> <code>ContentDigest
    off</code><br />
     <a href="directive-dict.html#Context"
    rel="Help"><strong>Context:</strong></a> server config, virtual
    host, directory, .htaccess<br />
     <a href="directive-dict.html#Override"
    rel="Help"><strong>Override:</strong></a> Options<br />
     <a href="directive-dict.html#Status"
    rel="Help"><strong>Status:</strong></a> experimental<br />
     <a href="directive-dict.html#Compatibility"
    rel="Help"><strong>Compatibility:</strong></a> ContentDigest is
    only available in Apache 1.1 and later 

    <p>This directive enables the generation of
    <code>Content-MD5</code> headers as defined in RFC1864
    respectively RFC2068.</p>

    <p>MD5 is an algorithm for computing a "message digest"
    (sometimes called "fingerprint") of arbitrary-length data, with
    a high degree of confidence that any alterations in the data
    will be reflected in alterations in the message digest.</p>

    <p>The <code>Content-MD5</code> header provides an end-to-end
    message integrity check (MIC) of the entity-body. A proxy or
    client may check this header for detecting accidental
    modification of the entity-body in transit. Example header:</p>
<pre>
   Content-MD5: AuLb7Dp1rqtRtxz2m9kRpA==
</pre>

    <p>Note that this can cause performance problems on your server
    since the message digest is computed on every request (the
    values are not cached).</p>

    <p><code>Content-MD5</code> is only sent for documents served
    by the core, and not by any module. For example, SSI documents,
    output from CGI scripts, and byte range responses do not have
    this header.</p>
    <hr />

    <h2><a id="coredumpdirectory"
    name="coredumpdirectory">CoreDumpDirectory directive</a></h2>

    <a href="directive-dict.html#Syntax"
    rel="Help"><strong>Syntax:</strong></a> CoreDumpDirectory
    <em>directory-path</em><br />
     <a href="directive-dict.html#Default"
    rel="Help"><strong>Default:</strong></a> the same location as
    ServerRoot<br />
     <a href="directive-dict.html#Context"
    rel="Help"><strong>Context:</strong></a> server config<br />
     <a href="directive-dict.html#Status"
    rel="Help"><strong>Status:</strong></a> core 

    <p>This controls the directory to which Apache attempts to
    switch before dumping core. The default is in the <a
    href="#serverroot">ServerRoot</a> directory, however since this
    should not be writable by the user the server runs as, core
    dumps won't normally get written. If you want a core dump for
    debugging, you can use this directive to place it in a
    different location.</p>

    <p>For example:</p>

    <blockquote>
    <code>CoreDumpDirectory /tmp</code>
    </blockquote>

    <hr />

    <h2><a id="defaulttype" name="defaulttype">DefaultType
    directive</a></h2>

    <a href="directive-dict.html#Syntax"
    rel="Help"><strong>Syntax:</strong></a> DefaultType
    <em>MIME-type</em><br />
     <a href="directive-dict.html#Default"
    rel="Help"><strong>Default:</strong></a> <code>DefaultType
    text/plain</code><br />
     <a href="directive-dict.html#Context"
    rel="Help"><strong>Context:</strong></a> server config, virtual
    host, directory, .htaccess<br />
     <a href="directive-dict.html#Override"
    rel="Help"><strong>Override:</strong></a> FileInfo<br />
     <a href="directive-dict.html#Status"
    rel="Help"><strong>Status:</strong></a> core 

    <p>There will be times when the server is asked to provide a
    document whose type cannot be determined by its MIME types
    mappings.</p>

    <p>The server must inform the client of the content-type of the
    document, so in the event of an unknown type it uses the
    <code>DefaultType</code>. For example:</p>

    <blockquote>
      <code>DefaultType image/gif</code>
    </blockquote>
    would be appropriate for a directory which contained many gif
    images with filenames missing the .gif extension. 

    <p><strong>See also:</strong> <a
    href="mod_mime.html#addtype">AddType</a> and <a
    href="mod_mime.html#typesconfig">TypesConfig</a>.</p>

    <hr />

    <h2><a id="directory" name="directory">&lt;Directory&gt;
    directive</a></h2>

    <a href="directive-dict.html#Syntax"
    rel="Help"><strong>Syntax:</strong></a> &lt;Directory
    <em>directory-path</em>|proxy:<em>url-path</em>&gt;
    ... &lt;/Directory&gt; <br />
     <a href="directive-dict.html#Context"
    rel="Help"><strong>Context:</strong></a> server config, virtual
    host<br />
     <a href="directive-dict.html#Status"
    rel="Help"><strong>Status:</strong></a> Core. 

    <p>&lt;Directory&gt; and &lt;/Directory&gt; are used to enclose
    a group of directives which will apply only to the named
    directory and sub-directories of that directory. Any directive
    which is allowed in a directory context may be used.
    <em>Directory-path</em> is either the full path to a directory,
    or a wild-card string. In a wild-card string, `?' matches any
    single character, and `*' matches any sequences of characters.
    As of Apache 1.3, you may also use `[ ]' character ranges like
    in the shell. Also as of Apache 1.3 none of the wildcards match
    a `/' character, which more closely mimics the behavior of
    Unix shells. Example:</p>
<pre>
   &lt;Directory /usr/local/httpd/htdocs&gt;
   Options Indexes FollowSymLinks
   &lt;/Directory&gt;
</pre>

    <p><strong>Apache 1.2 and above:</strong> Extended regular
    expressions can also be used, with the addition of the
    <code>~</code> character. For example:</p>
<pre>
   &lt;Directory ~ "^/www/.*/[0-9]{3}"&gt;
</pre>
    would match directories in /www/ that consisted of three
    numbers. 

    <p>If multiple (non-regular expression) directory sections
    match the directory (or its parents) containing a document,
    then the directives are applied in the order of shortest match
    first, interspersed with the directives from the <a
    href="#accessfilename">.htaccess</a> files. For example,
    with</p>

    <blockquote>
      <code>&lt;Directory /&gt;<br />
       AllowOverride None<br />
       &lt;/Directory&gt;<br />
      <br />
       &lt;Directory /home/*&gt;<br />
       AllowOverride FileInfo<br />
       &lt;/Directory&gt;</code>
    </blockquote>
    for access to the document <code>/home/web/dir/doc.html</code>
    the steps are: 

    <ul>
      <li>Apply directive <code>AllowOverride None</code>
      (disabling <code>.htaccess</code> files).</li>