core.html.en

apache 安装教程 apache 安装教程

    </p>
    <p>Note that by default <em>any</em> file in the specified 
    directory will be loaded as a configuration file.
    </p>
    <p>
    So make sure that you don't have stray files in
    this directory by mistake, such as temporary files created by your
    editor, for example.</p>

    <p><strong>See also:</strong> <a href="#include">Include</a> and <a
    href="#resourceconfig">ResourceConfig</a>.</p>
    <hr />

    <h2><a id="accessfilename" name="accessfilename">AccessFileName
    directive</a></h2>

    <a href="directive-dict.html#Syntax"
    rel="Help"><strong>Syntax:</strong></a> AccessFileName
    <em>filename</em> [<em>filename</em>] ...<br />
     <a href="directive-dict.html#Default"
    rel="Help"><strong>Default:</strong></a> <code>AccessFileName
    .htaccess</code><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<br />
     <a href="directive-dict.html#Compatibility"
    rel="Help"><strong>Compatibility:</strong></a> AccessFileName
    can accept more than one filename only in Apache 1.3 and later 

    <p>When returning a document to the client the server looks for
    the first existing access control file from this list of names
    in every directory of the path to the document, if access
    control files are enabled for that directory. For example:</p>

    <blockquote>
      <code>AccessFileName .acl</code>
    </blockquote>
    before returning the document /usr/local/web/index.html, the
    server will read /.acl, /usr/.acl, /usr/local/.acl and
    /usr/local/web/.acl for directives, unless they have been
    disabled with 

    <blockquote>
      <code>&lt;Directory /&gt;<br />
       AllowOverride None<br />
       &lt;/Directory&gt;</code>
    </blockquote>

    <p><strong>See Also:</strong> <a
    href="#allowoverride">AllowOverride</a> and <a
    href="../configuring.html">Configuration Files</a></p>
    <hr />

    <h2><a id="adddefaultcharset"
    name="adddefaultcharset">AddDefaultCharset directive</a></h2>
    <a href="directive-dict.html#Syntax"
    rel="Help"><strong>Syntax:</strong></a> AddDefaultCharset
    On|Off|<em>charset</em><br />
     <a href="directive-dict.html#Context"
    rel="Help"><strong>Context:</strong></a> all<br />
     <a href="directive-dict.html#Status"
    rel="Help"><strong>Status:</strong></a> core<br />
     <a href="directive-dict.html#Default"
    rel="Help"><strong>Default:</strong></a>
    <code>AddDefaultCharset Off</code><br />
     <a href="directive-dict.html#Compatibility"
    rel="Help"><strong>Compatibility:</strong></a>
    AddDefaultCharset is only available in Apache 1.3.12 and later 

    <p>This directive specifies the name of the character set that
    will be added to any response that does not have any parameter
    on the content type in the HTTP headers. This will override any
    character set specified in the body of the document via a
    <code>META</code> tag. A setting of <code>AddDefaultCharset
    Off</code> disables this functionality. <code>AddDefaultCharset
    On</code> enables Apache's internal default charset of
    <code>iso-8859-1</code> as required by the directive. You can
    also specify an alternate <em>charset</em> to be used.</p>
    
    <p>For example:</p>

    <blockquote>
    <code>AddDefaultCharset utf-8</code>
    </blockquote>

    <p><b>Note:</b> This will <b>not</b> have any effect on the
    Content-Type and character set for default Apache-generated
    status pages (such as '404 Not Found' or '301 Moved Permanently')
    because those have an <i>actual</i> character set (that in which the
    hard-coded page content is written) and don't need to have a default
    applied.</p>

    <hr />

    <h2><a id="addmodule" name="addmodule">AddModule
    directive</a></h2>

    <a href="directive-dict.html#Syntax"
    rel="Help"><strong>Syntax:</strong></a> AddModule
    <em>module</em> [<em>module</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> AddModule is
    only available in Apache 1.2 and later 

    <p>The server can have modules compiled in which are not
    actively in use. This directive can be used to enable the use
    of those modules. The server comes with a pre-loaded list of
    active modules; this list can be cleared with the <a
    href="#clearmodulelist">ClearModuleList</a> directive.</p>

    <p>For example:</p>

    <blockquote>
    <code>AddModule mod_include.c</code>
    </blockquote>

    <p>The ordering of <code>AddModule</code> lines is important.
    Modules are listed in reverse priority order --- the ones that come
    later can override the behavior of those that come earlier.  This
    can have visible effects; for instance, if UserDir followed Alias,
    you couldn't alias out a particular user's home directory.  For
    more information and a recommended ordering, see 
    <code>src/Configuration.tmpl</code> in the Apache source
    distribution.</p>

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

    <h2><a id="allowoverride" name="allowoverride">AllowOverride
    directive</a></h2>

    <a href="directive-dict.html#Syntax"
    rel="Help"><strong>Syntax:</strong></a> AllowOverride
    All|None|<em>directive-type</em> [<em>directive-type</em>]
    ...<br />
     <a href="directive-dict.html#Default"
    rel="Help"><strong>Default:</strong></a> <code>AllowOverride
    All</code><br />
     <a href="directive-dict.html#Context"
    rel="Help"><strong>Context:</strong></a> directory<br />
     <a href="directive-dict.html#Status"
    rel="Help"><strong>Status:</strong></a> core 

    <p>When the server finds an .htaccess file (as specified by <a
    href="#accessfilename">AccessFileName</a>) it needs to know
    which directives declared in that file can override earlier
    access information.</p>

    <p><strong>Note:</strong> <code>AllowOverride</code> is only
    valid in &lt;Directory&gt; sections, not in &lt;Location&gt; or
    &lt;Files&gt; sections, as implied by the <strong>Context</strong>
    section above.</p>

    <p>When this directive is set to <code>None</code>, then
    .htaccess files are completely ignored. In this case, the
    server will not even attempt to read .htaccess files in the
    filesystem.</p>

    <p>When this directive is set to <code>All</code>, then any
    directive which has the .htaccess <a
    href="directive-dict.html#Context">Context</a> is allowed in
    .htaccess files.</p>

    <p>The <em>directive-type</em> can be one of the following
    groupings of directives.</p>

    <dl>
      <dt>AuthConfig</dt>

      <dd>

      Allow use of the authorization directives (<a
      href="mod_auth_dbm.html#authdbmgroupfile">AuthDBMGroupFile</a>,
      <a
      href="mod_auth_dbm.html#authdbmuserfile">AuthDBMUserFile</a>,
      <a href="mod_auth.html#authgroupfile">AuthGroupFile</a>, <a
      href="#authname">AuthName</a>, <a
      href="#AuthDigestRealmSeed">AuthDigestRealmSeed</a>, <a
      href="#authtype">AuthType</a>, <a
      href="mod_auth.html#authuserfile">AuthUserFile</a>, <a
      href="#require">Require</a>, <em>etc.</em>).</dd>

      <dt>FileInfo</dt>

      <dd>
      Allow use of the directives controlling document types (<a
      href="mod_mime.html#addencoding">AddEncoding</a>, <a
      href="mod_mime.html#addlanguage">AddLanguage</a>, <a
      href="mod_mime.html#addtype">AddType</a>, <a
      href="#defaulttype">DefaultType</a>, <a
      href="#errordocument">ErrorDocument</a>, <a
      href="mod_negotiation.html#languagepriority">LanguagePriority</a>,
      <em>etc.</em>).</dd>

      <dt>Indexes</dt>

      <dd>
      Allow use of the directives controlling directory indexing
      (<a
      href="mod_autoindex.html#adddescription">AddDescription</a>,
      <a href="mod_autoindex.html#addicon">AddIcon</a>, <a
      href="mod_autoindex.html#addiconbyencoding">AddIconByEncoding</a>,
      <a href="mod_autoindex.html#addiconbytype">AddIconByType</a>,
      <a href="mod_autoindex.html#defaulticon">DefaultIcon</a>, <a
      href="mod_dir.html#directoryindex">DirectoryIndex</a>, <a
      href="mod_autoindex.html#fancyindexing">FancyIndexing</a>, <a
      href="mod_autoindex.html#headername">HeaderName</a>, <a
      href="mod_autoindex.html#indexignore">IndexIgnore</a>, <a
      href="mod_autoindex.html#indexoptions">IndexOptions</a>, <a
      href="mod_autoindex.html#readmename">ReadmeName</a>,
      <em>etc.</em>).</dd>

      <dt>Limit</dt>

      <dd>
      Allow use of the directives controlling host access (<a
      href="mod_access.html#allow">Allow</a>,
      <a href="mod_access.html#deny">Deny</a>
      and <a href="mod_access.html#order">Order</a>).</dd>

      <dt>Options</dt>

      <dd>
      Allow use of the directives controlling specific directory
      features (<a href="#options">Options</a> and <a
      href="mod_include.html#xbithack">XBitHack</a>).</dd>
    </dl>

    <p>Example:</p>
    <blockquote><code>AllowOverride AuthConfig Indexes</code></blockquote>

    <p><strong>See Also:</strong> <a
    href="#accessfilename">AccessFileName</a> and <a
    href="../configuring.html">Configuration Files</a></p>
    <hr />

    <h2><a id="authname" name="authname">AuthName
    directive</a></h2>

    <a href="directive-dict.html#Syntax"
    rel="Help"><strong>Syntax:</strong></a> AuthName
    <em>auth-domain</em><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> AuthConfig<br />
     <a href="directive-dict.html#Status"
    rel="Help"><strong>Status:</strong></a> core 

    <p>This directive sets the name of the authorization realm for
    a directory. This realm is given to the client so that the user
    knows which username and password to send.
    <samp>AuthName</samp> takes a single argument; if the realm
    name contains spaces, it must be enclosed in quotation marks.
    It must be accompanied by <a href="#authtype">AuthType</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>For example:</p>

    <blockquote><code>AuthName "Top Secret"</code></blockquote>

    <p>The string provided for the <code>AuthName</code> is what will
    appear in the password dialog provided by most browsers.</p>

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

    <h2><a id="AuthDigestRealmSeed" name="AuthDigestRealmSeed">AuthDigestRealmSeed
    directive</a></h2>

    <a href="directive-dict.html#Syntax"
    rel="Help"><strong>Syntax:</strong></a> AuthDigestRealmSeed
    <em>secret-real-string</em><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> AuthConfig<br />
     <a href="directive-dict.html#Status"
    rel="Help"><strong>Status:</strong></a> core

    <p>This directive sets a per realm secret nonce prefix
    which is used to ensure that a captured username, password
    and realm string during a Digest exchange cannot
    be replayed at other places.
    </p>
    <p>It only applies to <a href="mod_digest.html">mod_digest.html</a>,
    the experimental <a href="mod_auth_digest.html">mod_auth_digest.html</a>
    implements its own (more advanced and also time sensitive) replay protection.
    </p>

    It must be accompanied by <a href="#authtype">AuthType</a> of
    type Digest, one or more
    <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><strong>See also:</strong> <a
    href="../howto/auth.html">Authentication, Authorization, and
    Access Control</a></p>
    <hr />

    <h2><a id="authtype" name="authtype">AuthType
    directive</a></h2>

    <a href="directive-dict.html#Syntax"
    rel="Help"><strong>Syntax:</strong></a> AuthType
    Basic|Digest<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> AuthConfig<br />
     <a href="directive-dict.html#Status"
    rel="Help"><strong>Status:</strong></a> core