manual/mod/mod_include.html

	mod_include.html revision beba8a1afeca7426582177044e78b63d936785a4
45e9809aff7304721fddb95654901b32195c9c7avboxsync<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
45e9809aff7304721fddb95654901b32195c9c7avboxsync    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync<html xmlns="http://www.w3.org/1999/xhtml">
45e9809aff7304721fddb95654901b32195c9c7avboxsync  <head>
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <meta name="generator" content="HTML Tidy, see www.w3.org" />
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <title>Apache module mod_include</title>
45e9809aff7304721fddb95654901b32195c9c7avboxsync  </head>
45e9809aff7304721fddb95654901b32195c9c7avboxsync  <!-- Background white, links blue (unvisited), navy (visited), red (active) -->
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync  <body bgcolor="#FFFFFF" text="#000000" link="#0000FF"
45e9809aff7304721fddb95654901b32195c9c7avboxsync  vlink="#000080" alink="#FF0000">
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <!--#include virtual="header.html" -->
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <h1 align="CENTER">Module mod_include</h1>
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <p>This module provides for server-parsed html documents.</p>
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <p><a href="module-dict.html#Status"
45e9809aff7304721fddb95654901b32195c9c7avboxsync    rel="Help"><strong>Status:</strong></a> Base<br />
45e9809aff7304721fddb95654901b32195c9c7avboxsync     <a href="module-dict.html#SourceFile"
45e9809aff7304721fddb95654901b32195c9c7avboxsync    rel="Help"><strong>Source File:</strong></a>
45e9809aff7304721fddb95654901b32195c9c7avboxsync    mod_include.c<br />
45e9809aff7304721fddb95654901b32195c9c7avboxsync     <a href="module-dict.html#ModuleIdentifier"
45e9809aff7304721fddb95654901b32195c9c7avboxsync    rel="Help"><strong>Module Identifier:</strong></a>
45e9809aff7304721fddb95654901b32195c9c7avboxsync    includes_module</p>
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <h2>Summary</h2>
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <p>This module provides a filter which will process files
45e9809aff7304721fddb95654901b32195c9c7avboxsync    before they are sent to the client. The processing is
45e9809aff7304721fddb95654901b32195c9c7avboxsync    controlled by specially formated SGML comments, referred to as
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <em>elements</em>. These elements allow conditional text, the
45e9809aff7304721fddb95654901b32195c9c7avboxsync    inclusion other files or programs, as well as the setting and
45e9809aff7304721fddb95654901b32195c9c7avboxsync    printing of environment variables.</p>
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <h2>Directives</h2>
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <ul>
45e9809aff7304721fddb95654901b32195c9c7avboxsync      <li><a href="#xbithack">XBitHack</a></li>
45e9809aff7304721fddb95654901b32195c9c7avboxsync    </ul>
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <p>See also: <a href="core.html#options">Options</a>, <a
45e9809aff7304721fddb95654901b32195c9c7avboxsync    href="core.html.html#SetOutputFilter">SetOutputFilter</a>,
45e9809aff7304721fddb95654901b32195c9c7avboxsync    and <a href="core.html#acceptpathinfo">AcceptPathInfo</a>.</p>
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <h2>Enabling Server-Side Includes</h2>
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <p>Server Side Includes are implemented by the
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <code>INCLUDES</code> <a href="/filter.html">filter</a>. If
45e9809aff7304721fddb95654901b32195c9c7avboxsync    documents containing server-side include directives are given
45e9809aff7304721fddb95654901b32195c9c7avboxsync    the extension .shtml, the following directives will make Apache
45e9809aff7304721fddb95654901b32195c9c7avboxsync    parse them and assign the resulting document the mime type of
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <code>text/html</code>:</p>
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <blockquote>
45e9809aff7304721fddb95654901b32195c9c7avboxsync      <code>AddType text/html .shtml<br />
45e9809aff7304721fddb95654901b32195c9c7avboxsync            AddOutputFilter INCLUDES .shtml</code>
45e9809aff7304721fddb95654901b32195c9c7avboxsync    </blockquote>
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <p>The following directive must be given for the directories
45e9809aff7304721fddb95654901b32195c9c7avboxsync    containing the shtml files (typically in a
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <code>&lt;Directory&gt;</code> section, but this directive is
45e9809aff7304721fddb95654901b32195c9c7avboxsync    also valid .htaccess files if <code>AllowOverride
45e9809aff7304721fddb95654901b32195c9c7avboxsync    Options</code> is set):</p>
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <blockquote>
45e9809aff7304721fddb95654901b32195c9c7avboxsync      <code>Options +Includes</code>
45e9809aff7304721fddb95654901b32195c9c7avboxsync    </blockquote>
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <p>For backwards compatibility, the <code>server-parsed</code>
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <a href="/handler.html">handler</a> also activates the
45e9809aff7304721fddb95654901b32195c9c7avboxsync    INCLUDES filter. As well, Apache will activate the INCLUDES
45e9809aff7304721fddb95654901b32195c9c7avboxsync    filter for any document with mime type
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <code>text/x-server-parsed-html</code> or
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <code>text/x-server-parsed-html3</code> (and the resulting
45e9809aff7304721fddb95654901b32195c9c7avboxsync    output will have the mime type <code>text/html</code>).</p>
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <p>For more information, see our <a
45e9809aff7304721fddb95654901b32195c9c7avboxsync    href="/howto/ssi.html">Tutorial on Server Side
45e9809aff7304721fddb95654901b32195c9c7avboxsync    Includes</a>.</p>
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <h2>Basic Elements</h2>
45e9809aff7304721fddb95654901b32195c9c7avboxsync    The document is parsed as an HTML document, with special
45e9809aff7304721fddb95654901b32195c9c7avboxsync    commands embedded as SGML comments. A command has the syntax:
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <blockquote>
45e9809aff7304721fddb95654901b32195c9c7avboxsync      <code>&lt;!--#</code><em>element attribute=value
45e9809aff7304721fddb95654901b32195c9c7avboxsync      attribute=value ...</em> <code>--&gt;</code>
45e9809aff7304721fddb95654901b32195c9c7avboxsync    </blockquote>
45e9809aff7304721fddb95654901b32195c9c7avboxsync    The value will often be enclosed in double quotes; many
45e9809aff7304721fddb95654901b32195c9c7avboxsync    commands only allow a single attribute-value pair. Note that
45e9809aff7304721fddb95654901b32195c9c7avboxsync    the comment terminator (<samp>--&gt;</samp>) should be preceded
45e9809aff7304721fddb95654901b32195c9c7avboxsync    by whitespace to ensure that it isn't considered part of an SSI
45e9809aff7304721fddb95654901b32195c9c7avboxsync    token.
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <p>The allowed elements are:</p>
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync    <dl>
45e9809aff7304721fddb95654901b32195c9c7avboxsync      <dt><strong>config</strong></dt>
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync      <dd>
45e9809aff7304721fddb95654901b32195c9c7avboxsync        This command controls various aspects of the parsing. The
45e9809aff7304721fddb95654901b32195c9c7avboxsync        valid attributes are:
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync        <dl>
45e9809aff7304721fddb95654901b32195c9c7avboxsync          <dt>errmsg</dt>
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync          <dd>The value is a message that is sent back to the
45e9809aff7304721fddb95654901b32195c9c7avboxsync          client if an error occurs whilst parsing the
45e9809aff7304721fddb95654901b32195c9c7avboxsync          document.</dd>
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync          <dt>sizefmt</dt>
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync          <dd>The value sets the format to be used which displaying
45e9809aff7304721fddb95654901b32195c9c7avboxsync          the size of a file. Valid values are <code>bytes</code>
45e9809aff7304721fddb95654901b32195c9c7avboxsync          for a count in bytes, or <code>abbrev</code> for a count
45e9809aff7304721fddb95654901b32195c9c7avboxsync          in Kb or Mb as appropriate.</dd>
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync          <dt>timefmt</dt>
45e9809aff7304721fddb95654901b32195c9c7avboxsync
45e9809aff7304721fddb95654901b32195c9c7avboxsync          <dd>The value is a string to be used by the
45e9809aff7304721fddb95654901b32195c9c7avboxsync          <code>strftime(3)</code> library routine when printing
45e9809aff7304721fddb95654901b32195c9c7avboxsync          dates.</dd>
45e9809aff7304721fddb95654901b32195c9c7avboxsync        </dl>
      </dd>

      <dt><strong><a id="echo" name="echo">echo</a></strong></dt>

      <dd>
        This command prints one of the include variables, defined
        below. If the variable is unset, it is printed as
        <code>(none)</code>. Any dates printed are subject to the
        currently configured <code>timefmt</code>. Attributes:

        <dl>
          <dt>var</dt>

          <dd>The value is the name of the variable to print.</dd>

          <dt>encoding</dt>

          <dd>Specifies how Apache should encode special characters
          contained in the variable before outputting them. If set
          to "none", no encoding will be done. If set to "url",
          then URL encoding (also known as %-encoding; this is
          appropriate for use within URLs in links, etc.) will be
          performed. At the start of an <code>echo</code> element,
          the default is set to "entity", resulting in entity
          encoding (which is appropriate in the context of a
          block-level HTML element, eg. a paragraph of text). This
          can be changed by adding an <code>encoding</code>
          attribute, which will remain in effect until the next
          <code>encoding</code> attribute is encountered or the
          element ends, whichever comes first. Note that the
          <code>encoding</code> attribute must <em>precede</em> the
          corresponding <code>var</code> attribute to be effective,
          and that only special characters as defined in the
          ISO-8859-1 character encoding will be encoded. This
          encoding process may not have the desired result if a
          different character encoding is in use. Apache 1.3.12 and
          above; previous versions do no encoding.</dd>
        </dl>
      </dd>

      <dt><strong>exec</strong></dt>

      <dd>
        The exec command executes a given shell command or CGI
        script. The IncludesNOEXEC <a
        href="core.html#options">Option</a> disables this command
        completely. The valid attributes are:

        <dl>
          <dt>cgi</dt>

          <dd>
            The value specifies a (%-encoded) URL relative path to
            the CGI script. If the path does not begin with a (/),
            then it is taken to be relative to the current
            document. The document referenced by this path is
            invoked as a CGI script, even if the server would not
            normally recognize it as such. However, the directory
            containing the script must be enabled for CGI scripts
            (with <a
            href="mod_alias.html#scriptalias">ScriptAlias</a> or
            the ExecCGI <a href="core.html#options">Option</a>).

            <p>The CGI script is given the PATH_INFO and query
            string (QUERY_STRING) of the original request from the
            client; these cannot be specified in the URL path. The
            include variables will be available to the script in
            addition to the standard <a href="mod_cgi.html">CGI</a>
            environment.</p>

            <p>If the script returns a Location: header instead of
            output, then this will be translated into an HTML
            anchor.</p>

            <p>The <code>include virtual</code> element should be
            used in preference to <code>exec cgi</code>.</p>
          </dd>

          <dt>cmd</dt>

          <dd>The server will execute the given string using
          <code>/bin/sh</code>. The include variables are available
          to the command.</dd>
        </dl>
      </dd>

      <dt><strong>fsize</strong></dt>

      <dd>
        This command prints the size of the specified file, subject
        to the <code>sizefmt</code> format specification.
        Attributes:

        <dl>
          <dt>file</dt>

          <dd>The value is a path relative to the directory
          containing the current document being parsed.</dd>

          <dt>virtual</dt>

          <dd>The value is a (%-encoded) URL-path relative to the
          current document being parsed. If it does not begin with
          a slash (/) then it is taken to be relative to the
          current document.</dd>
        </dl>
      </dd>

      <dt><strong>flastmod</strong></dt>

      <dd>This command prints the last modification date of the
      specified file, subject to the <code>timefmt</code> format
      specification. The attributes are the same as for the
      <code>fsize</code> command.</dd>

      <dt><strong>include</strong></dt>

      <dd>
        This command inserts the text of another document or file
        into the parsed file. Any included file is subject to the
        usual access control. If the directory containing the
        parsed file has the <a href="core.html#options">Option</a>
        IncludesNOEXEC set, and the including the document would
        cause a program to be executed, then it will not be
        included; this prevents the execution of CGI scripts.
        Otherwise CGI scripts are invoked as normal using the
        complete URL given in the command, including any query
        string.
        <!--%plaintext &lt;?INDEX CGI scripts, {\tt include} element and&gt; -->


        <p>An attribute defines the location of the document; the
        inclusion is done for each attribute given to the include
        command. The valid attributes are:</p>

        <dl>
          <dt>file</dt>

          <dd>The value is a path relative to the directory
          containing the current document being parsed. It cannot
          contain <code>../</code>, nor can it be an absolute path.
          The <code>virtual</code> attribute should always be used
          in preference to this one.</dd>

          <dt>virtual</dt>

          <dd>The value is a (%-encoded) URL relative to the
          current document being parsed. The URL cannot contain a
          scheme or hostname, only a path and an optional query
          string. If it does not begin with a slash (/) then it is
          taken to be relative to the current document.</dd>
        </dl>
        A URL is constructed from the attribute, and the output the
        server would return if the URL were accessed by the client
        is included in the parsed output. Thus included files can
        be nested.
      </dd>

      <dt><strong>printenv</strong></dt>

      <dd>This prints out a listing of all existing variables and
      their values. Starting with Apache 1.3.12, special characters
      are entity encoded (see the <a
      href="#echo"><code>echo</code></a> element for details)
      before being output. No attributes.</dd>

      <dd>For example: <code>&lt;!--#printenv --&gt;</code></dd>

      <dd>Apache 1.2 and above.</dd>

      <dt><strong>set</strong></dt>

      <dd>
        This sets the value of a variable. Attributes:

        <dl>
          <dt>var</dt>

          <dd>The name of the variable to set.</dd>

          <dt>value</dt>

          <dd>The value to give a variable.</dd>
        </dl>
        For example: <code>&lt;!--#set var="category" value="help"
        --&gt;</code>
      </dd>

      <dd>Apache 1.2 and above.</dd>
    </dl>

    <h2>Include Variables</h2>
    In addition to the variables in the standard CGI environment,
    these are available for the <code>echo</code> command, for
    <code>if</code> and <code>elif</code>, and to any program
    invoked by the document.

    <dl>
      <dt>DATE_GMT</dt>

      <dd>The current date in Greenwich Mean Time.</dd>

      <dt>DATE_LOCAL</dt>

      <dd>The current date in the local time zone.</dd>

      <dt>DOCUMENT_NAME</dt>

      <dd>The filename (excluding directories) of the document
      requested by the user.</dd>

      <dt>DOCUMENT_URI</dt>

      <dd>The (%-decoded) URL path of the document requested by the
      user. Note that in the case of nested include files, this is
      <em>not</em> then URL for the current document.</dd>

      <dt>LAST_MODIFIED</dt>

      <dd>The last modification date of the document requested by
      the user.</dd>
    </dl>

    <h2>Variable Substitution</h2>

    <p>Variable substitution is done within quoted strings in most
    cases where they may reasonably occur as an argument to an SSI
    directive. This includes the <samp>config</samp>,
    <samp>exec</samp>, <samp>flastmod</samp>, <samp>fsize</samp>,
    <samp>include</samp>, and <samp>set</samp> directives, as well
    as the arguments to conditional operators. You can insert a
    literal dollar sign into the string using backslash
    quoting:</p>
<pre>
    &lt;!--#if expr="$a = \$test" --&gt;
</pre>

    <p>If a variable reference needs to be substituted in the
    middle of a character sequence that might otherwise be
    considered a valid identifier in its own right, it can be
    disambiguated by enclosing the reference in braces,
    <em>&agrave; la</em> shell substitution:</p>
<pre>
    &lt;!--#set var="Zed" value="${REMOTE_HOST}_${REQUEST_METHOD}" --&gt;
</pre>

    <p>This will result in the <samp>Zed</samp> variable being set
    to "<samp>X_Y</samp>" if <samp>REMOTE_HOST</samp> is
    "<samp>X</samp>" and <samp>REQUEST_METHOD</samp> is
    "<samp>Y</samp>".</p>

    <p>EXAMPLE: the below example will print "in foo" if the
    DOCUMENT_URI is /foo/file.html, "in bar" if it is
    /bar/file.html and "in neither" otherwise:</p>
<pre>
    &lt;!--#if expr="\"$DOCUMENT_URI\" = \"/foo/file.html\"" --&gt;
    in foo
    &lt;!--#elif expr="\"$DOCUMENT_URI\" = \"/bar/file.html\"" --&gt;
    in bar
    &lt;!--#else --&gt;
    in neither
    &lt;!--#endif --&gt;
</pre>

    <h2><a id="flowctrl" name="flowctrl">Flow Control
    Elements</a></h2>
    These are available in Apache 1.2 and above. The basic flow
    control elements are:
<pre>
    &lt;!--#if expr="<em>test_condition</em>" --&gt;
    &lt;!--#elif expr="<em>test_condition</em>" --&gt;
    &lt;!--#else --&gt;
    &lt;!--#endif --&gt;
</pre>

    <p>The <strong><code>if</code></strong> element works like an
    if statement in a programming language. The test condition is
    evaluated and if the result is true, then the text until the
    next <strong><code>elif</code></strong>,
    <strong><code>else</code></strong>. or
    <strong><code>endif</code></strong> element is included in the
    output stream.</p>

    <p>The <strong><code>elif</code></strong> or
    <strong><code>else</code></strong> statements are be used the
    put text into the output stream if the original test_condition
    was false. These elements are optional.</p>

    <p>The <strong><code>endif</code></strong> element ends the
    <strong><code>if</code></strong> element and is required.</p>

    <p><em>test_condition</em> is one of the following:</p>

    <dl>
      <dt><em>string</em></dt>

      <dd>true if <em>string</em> is not empty</dd>

      <dt><em>string1</em> = <em>string2</em><br />
       <em>string1</em> != <em>string2</em><br />
       <em>string1</em> &lt; <em>string2</em><br />
       <em>string1</em> &lt;= <em>string2</em><br />
       <em>string1</em> &gt; <em>string2</em><br />
       <em>string1</em> &gt;= <em>string2</em></dt>

      <dd>Compare string1 with string 2. If string2 has the form
      <em>/string/</em> then it is compared as a regular
      expression. Regular expressions have the same syntax as those
      found in the Unix <samp>egrep</samp> command.</dd>

      <dt>( <em>test_condition</em> )</dt>

      <dd>true if <em>test_condition</em> is true</dd>

      <dt>! <em>test_condition</em></dt>

      <dd>true if <em>test_condition</em> is false</dd>

      <dt><em>test_condition1</em> &amp;&amp;
      <em>test_condition2</em></dt>

      <dd>true if both <em>test_condition1</em> and
      <em>test_condition2</em> are true</dd>

      <dt><em>test_condition1</em> || <em>test_condition2</em></dt>

      <dd>true if either <em>test_condition1</em> or
      <em>test_condition2</em> is true</dd>
    </dl>

    <p>"<em>=</em>" and "<em>!=</em>" bind more tightly than
    "<em>&amp;&amp;</em>" and "<em>||</em>". "<em>!</em>" binds
    most tightly. Thus, the following are equivalent:</p>
<pre>
    &lt;!--#if expr="$a = test1 &amp;&amp; $b = test2" --&gt;
    &lt;!--#if expr="($a = test1) &amp;&amp; ($b = test2)" --&gt;
</pre>

    <p>Anything that's not recognized as a variable or an operator
    is treated as a string. Strings can also be quoted:
    <em>'string'</em>. Unquoted strings can't contain whitespace
    (blanks and tabs) because it is used to separate tokens such as
    variables. If multiple strings are found in a row, they are
    concatenated using blanks. So,</p>
<pre>
     <em>string1    string2</em>  results in <em>string1 string2</em>
    <em>'string1    string2'</em> results in <em>string1    string2</em>
</pre>

    <h2>Using Server Side Includes for ErrorDocuments</h2>
    There is <a href="/misc/custom_errordocs.html">a document</a>
    which describes how to use the features of mod_include to offer
    internationalized customized server error documents.

    <h2>PATH_INFO with Server Side Includes</h2>

    <p>Files processed for server-side includes no longer accept
    requests with PATH_INFO (trailing pathname information) by
    default.  You can use the <a
    href="core.html#AcceptPathInfo">AcceptPathInfo</a> directive to
    configure the server to accept requests with PATH_INFO.</p>

    <hr />

    <h2><a id="xbithack" name="xbithack">XBitHack</a>
    directive</h2>
    <!--%plaintext &lt;?INDEX {\tt XBitHack} directive&gt; -->
    <a href="directive-dict.html#Syntax"
    rel="Help"><strong>Syntax:</strong></a> XBitHack
    on|off|full<br />
     <a href="directive-dict.html#Default"
    rel="Help"><strong>Default:</strong></a> <code>XBitHack
    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> Base<br />
     <a href="directive-dict.html#Module"
    rel="Help"><strong>Module:</strong></a> mod_include

    <p>The XBitHack directives controls the parsing of ordinary
    html documents. This directive only affects files associated
    with the MIME type <code>text/html</code>. XBitHack can take on
    the following values:</p>

    <dl>
      <dt>off</dt>

      <dd>No special treatment of executable files.</dd>

      <dt>on</dt>

      <dd>Any text/html file that has the user-execute bit set will
      be treated as a server-parsed html document.</dd>

      <dt>full</dt>

      <dd>
        As for <code>on</code> but also test the group-execute bit.
        If it is set, then set the Last-modified date of the
        returned file to be the last modified time of the file. If
        it is not set, then no last-modified date is sent. Setting
        this bit allows clients and proxies to cache the result of
        the request.

        <p><strong>Note:</strong> you would not want to use the full
        option, unless you assure the group-execute bit is unset for
        every SSI script which might <code>#include</code> a CGI
        or otherwise produces different output on each hit (or could
        potentially change on subsequent requests).</p>
      </dd>
    </dl>

    <p><!--#include virtual="footer.html" -->
    </p>
  </body>
</html>