manual/mod/mod_cern_meta.xml

	mod_cern_meta.xml revision 7db9f691a00ead175b03335457ca296a33ddf31b
2N/A<?xml version="1.0"?>
2N/A<!DOCTYPE modulesynopsis SYSTEM "/style/modulesynopsis.dtd">
2N/A<?xml-stylesheet type="text/xsl" href="/style/manual.en.xsl"?>
2N/A<modulesynopsis metafile="mod_cern_meta.xml.meta">
2N/A
2N/A<name>mod_cern_meta</name>
2N/A<description>CERN httpd metafile semantics</description>
2N/A<status>Extension</status>
2N/A<sourcefile>mod_cern_meta.c</sourcefile>
2N/A<identifier>cern_meta_module</identifier>
2N/A
2N/A<summary>
2N/A    <p>Emulate the CERN HTTPD Meta file semantics. Meta files are HTTP
2N/A    headers that can be output in addition to the normal range of
2N/A    headers for each file accessed. They appear rather like the
2N/A    Apache .asis files, and are able to provide a crude way of
2N/A    influencing the Expires: header, as well as providing other
2N/A    curiosities. There are many ways to manage meta information,
2N/A    this one was chosen because there is already a large number of
2N/A    CERN users who can exploit this module.</p>
2N/A
2N/A    <p>More information on the <a
2N/A    href="http://www.w3.org/pub/WWW/Daemon/User/Config/General.html#MetaDir"
2N/A    >CERN metafile semantics</a> is available.</p>
2N/A</summary>
2N/A
2N/A<seealso><module>mod_headers</module></seealso>
2N/A<seealso><module>mod_asis</module></seealso>
2N/A
2N/A<directivesynopsis>
2N/A<name>MetaFiles</name>
2N/A<description>Activates CERN meta-file processing</description>
2N/A<syntax>MetaFiles on|off</syntax>
2N/A<default>MetaFiles off</default>
2N/A<contextlist><context>server config</context>
2N/A<context>virtual host</context>
2N/A<context>directory</context>
2N/A<context>.htaccess</context></contextlist>
2N/A<override>Indexes</override>
2N/A
2N/A<usage>
    <p>Turns on/off Meta file processing on a per-directory basis.</p>
</usage>
</directivesynopsis>

<directivesynopsis>
<name>MetaDir</name>
<description>Name of the directory to find CERN-style meta information
files</description>
<syntax>MetaDir <var>directory</var></syntax>
<default>MetaDir .web</default>
<contextlist><context>server config</context>
<context>virtual host</context>
<context>directory</context>
<context>.htaccess</context></contextlist>
<override>Indexes</override>

<usage>
    <p>Specifies the name of the directory in which Apache can find
    meta information files. The directory is usually a 'hidden'
    subdirectory of the directory that contains the file being
    accessed. Set to "<code>.</code>" to look in the same directory
    as the file:</p>

    <example>MetaDir .</example>

    <p>Or, to set it to a subdirectory of the directory containing the
    files:</p>

    <example>MetaDir .meta</example>
</usage>
</directivesynopsis>

<directivesynopsis>
<name>MetaSuffix</name>
<description>File name suffix for the file containg CERN-style
meta information</description>
<syntax>MetaSuffix <var>suffix</var></syntax>
<default>MetaSuffix .meta</default>
<contextlist><context>server config</context>
<context>virtual host</context>
<context>directory</context>
<context>.htaccess</context></contextlist>
<override>Indexes</override>

<usage>
    <p>Specifies the file name suffix for the file containing the
    meta information. For example, the default values for the two
    directives will cause a request to
    <code>DOCUMENT_ROOT/somedir/index.html</code> to look in
    <code>DOCUMENT_ROOT/somedir/.web/index.html.meta</code> and
    will use its contents to generate additional MIME header
    information.</p>

    <example><title>Example:</title>
      MetaSuffix .meta
    </example>
</usage>
</directivesynopsis>

</modulesynopsis>