mod_autoindex.html.en

linux服务器 源码。。。。。。。。。。。。。。

      basically broken into two components, the files and the
      subdirectories, and each is sorted separately and then
      displayed subdirectories-first. For instance, if the sort
      order is descending by name, and <samp>FoldersFirst</samp> is
      enabled, subdirectory <samp>Zed</samp> will be listed before
      subdirectory <samp>Beta</samp>, which will be listed before
      normal files <samp>Gamma</samp> and <samp>Alpha</samp>.
      <b>This option only has an effect if <a
      href="#indexoptions:fancyindexing"><samp>FancyIndexing</samp></a>
      is also enabled.</b></dd>

      <dt><a id="indexoptions:iconheight"
      name="indexoptions:iconheight">IconHeight[=pixels]
      (<em>Apache 1.3 and later</em>)</a></dt>

      <dd>

      Presence of this option, when used with IconWidth, will cause
      the server to include <samp>HEIGHT</samp> and
      <samp>WIDTH</samp> attributes in the <samp>IMG</samp> tag for
      the file icon. This allows browser to precalculate the page
      layout without having to wait until all the images have been
      loaded. If no value is given for the option, it defaults to
      the standard height of the icons supplied with the Apache
      software.</dd>

      <dt><a id="indexoptions:iconsarelinks"
      name="indexoptions:iconsarelinks">IconsAreLinks</a></dt>

      <dd>

      This makes the icons part of the anchor for the filename, for
      fancy indexing.</dd>

      <dt><a id="indexoptions:iconwidth"
      name="indexoptions:iconwidth">IconWidth[=pixels] (<em>Apache
      1.3 and later</em>)</a></dt>

      <dd>

      Presence of this option, when used with IconHeight, will
      cause the server to include <samp>HEIGHT</samp> and
      <samp>WIDTH</samp> attributes in the <samp>IMG</samp> tag for
      the file icon. This allows browser to precalculate the page
      layout without having to wait until all the images have been
      loaded. If no value is given for the option, it defaults to
      the standard width of the icons supplied with the Apache
      software.</dd>

      <dt><a id="indexoptions:ignorecase"
      name="indexoptions:ignorecase">IgnoreCase</a>
      (<em>Apache 1.3.24 and later</em>)</dt>

      <dd>
      If this option is enabled, names are sorted in case-insensitive
      manner.  For instance, if the sort order is ascending by name,
      and <samp>IgnoreCase</samp> is enabled, file <samp>Zeta</samp>
      will be listed after file <samp>alfa</samp> (Note: file
      <samp>GAMMA</samp> will always be listed before file
      <samp>gamma</samp>). <b>This option only has an effect if <a
      href="#indexoptions:fancyindexing"><samp>FancyIndexing</samp></a>
      is also enabled.</b></dd>

      <dt><a id="indexoptions:namewidth"
      name="indexoptions:namewidth">NameWidth=[<em>n</em> | *]
      (<em>Apache 1.3.2 and later</em>)</a></dt>

      <dd>The NameWidth keyword allows you to specify the width of
      the filename column in bytes. If the keyword value is
      '<samp>*</samp>', then the column is automatically sized to
      the length of the longest filename in the display.</dd>

      <dt><a id="indexoptions:scanhtmltitles"
      name="indexoptions:scanhtmltitles">ScanHTMLTitles</a></dt>

      <dd>

      This enables the extraction of the title from HTML documents
      for fancy indexing. If the file does not have a description
      given by <a href="#adddescription">AddDescription</a> then
      httpd will read the document for the value of the TITLE tag.
      This is CPU and disk intensive.</dd>

      <dt><a id="indexoptions:suppresscolumnsorting"
      name="indexoptions:suppresscolumnsorting">SuppressColumnSorting</a></dt>

      <dd>

      If specified, Apache will not make the column headings in a
      FancyIndexed directory listing into links for sorting. The
      default behavior is for them to be links; selecting the
      column heading will sort the directory listing by the values
      in that column. <strong>Only available in Apache 1.3 and
      later.</strong></dd>

      <dt><a id="indexoptions:suppressdescription"
      name="indexoptions:suppressdescription">SuppressDescription</a></dt>

      <dd>

      This will suppress the file description in fancy indexing
      listings. By default, no file descriptions are defined, and
      so the use of this option will regain 23 characters of screen
      space to use for something else. See <a
      href="#adddescription"><samp>AddDescription</samp></a> for
      information about setting the file description. See also the
      <a
      href="#indexoptions:descriptionwidth"><samp>DescriptionWidth</samp></a>
      index option to limit the size of the description
      column.</dd>

      <dt><a id="indexoptions:suppresshtmlpreamble"
      name="indexoptions:suppresshtmlpreamble">SuppressHTMLPreamble</a>
      (<em>Apache 1.3 and later</em>)</dt>

      <dd>

      If the directory actually contains a file specified by the <a
      href="#headername">HeaderName</a> directive, the module
      usually includes the contents of the file after a standard
      HTML preamble (&lt;HTML&gt;, &lt;HEAD&gt;, <em>et
      cetera</em>). The SuppressHTMLPreamble option disables this
      behavior, causing the module to start the display with the
      header file contents. The header file must contain
      appropriate HTML instructions in this case. If there is no
      header file, the preamble is generated as usual.</dd>

      <dt><a id="indexoptions:suppresslastmodified"
      name="indexoptions:suppresslastmodified">SuppressLastModified</a></dt>

      <dd>

      This will suppress the display of the last modification date,
      in fancy indexing listings.</dd>

      <dt><a id="indexoptions:suppresssize"
      name="indexoptions:suppresssize">SuppressSize</a></dt>

      <dd>

      This will suppress the file size in fancy indexing
      listings.</dd>

      <dt><a id="indexoptions:trackmodified"
      name="indexoptions:trackmodified">TrackModified (<em>Apache
      1.3.15 and later</em>)</a></dt>

      <dd>

      This returns the Last-Modified and ETag values for the listed
      directory in the HTTP header. It is only valid if the
      operating system and file system return legitimate stat()
      results. Most Unix systems do so, as do OS2's JFS and Win32's
      NTFS volumes. OS2 and Win32 FAT volumes, for example, do not.
      Once this feature is enabled, the client or proxy can track
      changes to the list of files when they perform a HEAD
      request. Note some operating systems correctly track new and
      removed files, but do not track changes for sizes or dates of
      the files within the directory.</dd>
    </dl>

    <p>There are some noticeable differences in the behavior of
    this directive in recent (post-1.3.0) versions of Apache.</p>

    <dl>
      <dt>Apache 1.3.2 and earlier:</dt>

      <dd>
        <p>The default is that no options are enabled. If multiple
        IndexOptions could apply to a directory, then the most
        specific one is taken complete; the options are not merged.
        For example:</p>

        <blockquote>
<pre>
&lt;Directory /web/docs&gt;
    IndexOptions FancyIndexing
&lt;/Directory&gt;
&lt;Directory /web/docs/spec&gt;
    IndexOptions ScanHTMLTitles
&lt;/Directory&gt;
</pre>
        </blockquote>
        then only <code>ScanHTMLTitles</code> will be set for the
        /web/docs/spec directory.
      </dd>

      <dt>Apache 1.3.3 and later:</dt>

      <dd>
        <p>Apache 1.3.3 introduced some significant changes in the
        handling of <samp>IndexOptions</samp> directives. In
        particular,</p>

        <ul>
          <li>Multiple <samp>IndexOptions</samp> directives for a
          single directory are now merged together. The result of
          the example above will now be the equivalent of
          <code>IndexOptions&nbsp;FancyIndexing&nbsp;ScanHTMLTitles</code>.</li>

          <li>The addition of the incremental syntax
          (<em>i.e.</em>, prefixing keywords with '+' or '-').</li>
        </ul>

        <p>Whenever a '+' or '-' prefixed keyword is encountered,
        it is applied to the current <samp>IndexOptions</samp>
        settings (which may have been inherited from an upper-level
        directory). However, whenever an unprefixed keyword is
        processed, it clears all inherited options and any
        incremental settings encountered so far. Consider the
        following example:</p>

        <blockquote>
          <code>IndexOptions +ScanHTMLTitles -IconsAreLinks
          FancyIndexing<br />
           IndexOptions +SuppressSize<br />
          </code>
        </blockquote>

        <p>The net effect is equivalent to
        <code>IndexOptions&nbsp;FancyIndexing&nbsp;+SuppressSize</code>,
        because the unprefixed <code>FancyIndexing</code> discarded
        the incremental keywords before it, but allowed them to
        start accumulating again afterward.</p>

        <p>To unconditionally set the <code>IndexOptions</code> for
        a particular directory, clearing the inherited settings,
        specify keywords without either '+' or '-' prefixes.</p>
      </dd>
    </dl>
    <hr />

    <h2><a id="indexorderdefault"
    name="indexorderdefault">IndexOrderDefault</a> directive</h2>

    <a href="directive-dict.html#Syntax"
    rel="Help"><strong>Syntax:</strong></a> IndexOrderDefault
    Ascending|Descending Name|Date|Size|Description <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> Indexes <br />
     <a href="directive-dict.html#Status"
    rel="Help"><strong>Status:</strong></a> Base <br />
     <a href="directive-dict.html#Module"
    rel="Help"><strong>Module:</strong></a> mod_autoindex <br />
     <a href="directive-dict.html#Compatibility"
    rel="Help"><strong>Compatibility:</strong></a>
    IndexOrderDefault is only available in Apache 1.3.4 and later. 

    <p>The <samp>IndexOrderDefault</samp> directive is used in
    combination with the <a
    href="#indexoptions:fancyindexing"><samp>FancyIndexing</samp></a>
    index option. By default, fancyindexed directory listings are
    displayed in ascending order by filename; the
    <samp>IndexOrderDefault</samp> allows you to change this
    initial display order.</p>

    <p><samp>IndexOrderDefault</samp> takes two arguments. The
    first must be either <samp>Ascending</samp> or
    <samp>Descending</samp>, indicating the direction of the sort.
    The second argument must be one of the keywords
    <samp>Name</samp>, <samp>Date</samp>, <samp>Size</samp>, or
    <samp>Description</samp>, and identifies the primary key. The
    secondary key is <em>always</em> the ascending filename.</p>

    <p>You can force a directory listing to only be displayed in a
    particular order by combining this directive with the <a
    href="#indexoptions:suppresscolumnsorting"><samp>SuppressColumnSorting</samp></a>
    index option; this will prevent the client from requesting the
    directory listing in a different order.</p>
    <hr />

    <h2><a id="readmename" name="readmename">ReadmeName</a>
    directive</h2>

    <a href="directive-dict.html#Syntax"
    rel="Help"><strong>Syntax:</strong></a> ReadmeName
    <em>filename</em><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> Indexes<br />
     <a href="directive-dict.html#Status"
    rel="Help"><strong>Status:</strong></a> Base<br />
     <a href="directive-dict.html#Module"
    rel="Help"><strong>Module:</strong></a> mod_autoindex <br />
     <a href="directive-dict.html#Compatibility"
    rel="Help"><strong>Compatibility:</strong></a> some features
    only available after 1.3.6; see text 

    <p>The ReadmeName directive sets the name of the file that will
    be appended to the end of the index listing. <em>Filename</em>
    is the name of the file to include, and is taken to be relative
    to the location being indexed.</p>

    <blockquote>
      <strong>The <em>filename</em> argument is treated as a stub
      filename in Apache 1.3.6 and earlier, and as a relative URI
      in later versions. Details of how it is handled may be found
      under the description of the <a
      href="#headername">HeaderName</a> directive, which uses the
      same mechanism and changed at the same time as
      ReadmeName.</strong>
    </blockquote>

    <p>See also <a href="#headername">HeaderName</a>.</p>

    <p>    <hr />

    <h3 align="CENTER">Apache HTTP Server Version 1.3</h3>
    <a href="./"><img src="../images/index.gif" alt="Index" /></a>
    <a href="../"><img src="../images/home.gif" alt="Home" /></a>

    </p>
  </body>
</html>