httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From n.@apache.org
Subject cvs commit: httpd-2.0/docs/manual/mod mod_filter.html.en quickreference.html.de quickreference.html.en quickreference.html.es quickreference.html.ja.euc-jp quickreference.html.ko.euc-kr
Date Fri, 15 Oct 2004 22:48:45 GMT
nd          2004/10/15 15:48:45

  Modified:    docs/manual/mod mod_filter.html.en quickreference.html.de
                        quickreference.html.en quickreference.html.es
                        quickreference.html.ja.euc-jp
                        quickreference.html.ko.euc-kr
  Log:
  update transformation
  
  Revision  Changes    Path
  1.5       +305 -268  httpd-2.0/docs/manual/mod/mod_filter.html.en
  
  Index: mod_filter.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_filter.html.en,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -u -r1.4 -r1.5
  --- mod_filter.html.en	15 Oct 2004 21:21:45 -0000	1.4
  +++ mod_filter.html.en	15 Oct 2004 22:48:44 -0000	1.5
  @@ -27,21 +27,20 @@
   <tr><th><a href="module-dict.html#Status">Status:</a></th><td>Extension</td></tr>
   <tr><th><a href="module-dict.html#ModuleIdentifier">ModuleIdentifier:</a></th><td>filter_module</td></tr>
   <tr><th><a href="module-dict.html#SourceFile">SourceFile:</a></th><td>mod_filter.c</td></tr>
  -<tr><th><a href="module-dict.html#Compatibility">Compatibility:</a></th><td>Apache 2.0 and higher</td></tr></table>
  +<tr><th><a href="module-dict.html#Compatibility">Compatibility:</a></th><td>Version 2.1 and higher</td></tr></table>
   <h3>Summary</h3>
   
  -<p>This module enables smart, context-sensitive configuration of
  -output content filters.  For example, apache can be configured to
  -process different content-types through different filters, even
  -when the content-type is not known in advance (e.g. in a proxy).
  -</p>
  -<p>mod_filter works by introducing indirection into the filter
  -chain.  Instead of inserting filters in the chain, we insert
  -a filter harness which in turn dispatches conditionally
  -to a filter provider.  Any content filter may be used as a provider
  -to mod_filter; no change to existing filter modules is required
  -(although it may be possible to simplify them).
  -</p>
  +    <p>This module enables smart, context-sensitive configuration of
  +    output content filters.  For example, apache can be configured to
  +    process different content-types through different filters, even
  +    when the content-type is not known in advance (e.g. in a proxy).</p>
  +
  +    <p><code class="module"><a href="../mod/mod_filter.html">mod_filter</a></code> works by introducing indirection into
  +    the filter chain.  Instead of inserting filters in the chain, we insert
  +    a filter harness which in turn dispatches conditionally
  +    to a filter provider.  Any content filter may be used as a provider
  +    to <code class="module"><a href="../mod/mod_filter.html">mod_filter</a></code>; no change to existing filter modules is
  +    required (although it may be possible to simplify them).</p>
   </div>
   <div id="quickview"><h3 class="directives">Directives</h3>
   <ul id="toc">
  @@ -62,183 +61,203 @@
   <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
   <div class="section">
   <h2><a name="smart" id="smart">Smart Filtering</a></h2>
  -<p>In the traditional filtering model, filters are inserted unconditionally
  -using <code class="directive"><a href="../mod/mod_mime.html#addoutputfilter">AddOutputFilter</a></code> and family.
  -Each filter then needs to determine whether to run, and there is little
  -flexibility available for server admins to allow the chain to be
  -configured dynamically.</p>
  -<p>mod_filter by contrast gives server administrators a great deal of
  -flexibility in configuring the filter chain.  In fact, filters can be
  -inserted based on any Request Header, Response Header or Environment
  -Variable.  This generalises the limited flexibility offered by
  -<code class="directive"><a href="../mod/core.html#addoutputfilterbytype">AddOutputFilterByType</a></code>, and fixes
  -it to work correctly with dynamic content, regardless of the
  -content generator.  The ability to dispatch based on Environment
  -Variables offers the full flexibility of configuration with
  -<code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> to anyone who needs it.</p>
  +    <p>In the traditional filtering model, filters are inserted unconditionally
  +    using <code class="directive"><a href="../mod/mod_mime.html#addoutputfilter">AddOutputFilter</a></code> and family.
  +    Each filter then needs to determine whether to run, and there is little
  +    flexibility available for server admins to allow the chain to be
  +    configured dynamically.</p>
   
  +    <p><code class="module"><a href="../mod/mod_filter.html">mod_filter</a></code> by contrast gives server administrators a
  +    great deal of flexibility in configuring the filter chain.  In fact,
  +    filters can be inserted based on any Request Header, Response Header
  +    or Environment Variable.  This generalises the limited flexibility offered
  +    by <code class="directive"><a href="../mod/core.html#addoutputfilterbytype">AddOutputFilterByType</a></code>, and fixes
  +    it to work correctly with dynamic content, regardless of the
  +    content generator.  The ability to dispatch based on Environment
  +    Variables offers the full flexibility of configuration with
  +    <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> to anyone who needs it.</p>
   </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
   <div class="section">
   <h2><a name="terms" id="terms">Filter Declarations, Providers and Chains</a></h2>
  -<p class="figure">
  -<img src="../images/mod_filter_old.gif" width="160" height="310" alt="[This image displays the traditional filter model]" /><br />
  -<dfn>Figure 1:</dfn> The traditional filter model</p>
  -
  -<p>In the traditional model, output filters are a simple chain
  -from the content generator (handler) to the client.  This works well
  -provided the filter chain can be correctly configured, but presents
  -problems when the filters need to be configured dynamically based on
  -the outcome of the handler.</p>
  -<p class="figure">
  -<img src="../images/mod_filter_new.gif" width="423" height="331" alt="[This image shows the mod_filter model]" /><br />
  -<dfn>Figure 2:</dfn> The <code class="module"><a href="../mod/mod_filter.html">mod_filter</a></code> model</p>
  -<p>mod_filter works by introducing indirection into the filter
  -chain.  Instead of inserting filters in the chain, we insert
  -a filter harness which in turn dispatches conditionally
  -to a filter provider.  Any content filter may be used as a provider
  -to mod_filter; no change to existing filter modules is required
  -(although it may be possible to simplify them).  There can be
  -multiple providers for one filter, but no more than one provider will
  -run for any single request.
  -</p>
  -<p>A filter chain comprises any number of instances of the filter
  -harness, each of which may have any number of providers.  A special
  -case is that of a single provider with unconditional dispatch: this
  -is equivalent to inserting the provider filter directly into the chain.
  -</p>
  +    <p class="figure">
  +    <img src="../images/mod_filter_old.gif" width="160" height="310" alt="[This image displays the traditional filter model]" /><br />
  +    <dfn>Figure 1:</dfn> The traditional filter model</p>
  +
  +    <p>In the traditional model, output filters are a simple chain
  +    from the content generator (handler) to the client.  This works well
  +    provided the filter chain can be correctly configured, but presents
  +    problems when the filters need to be configured dynamically based on
  +    the outcome of the handler.</p>
  +
  +    <p class="figure">
  +    <img src="../images/mod_filter_new.gif" width="423" height="331" alt="[This image shows the mod_filter model]" /><br />
  +    <dfn>Figure 2:</dfn> The <code class="module"><a href="../mod/mod_filter.html">mod_filter</a></code> model</p>
  +
  +    <p><code class="module"><a href="../mod/mod_filter.html">mod_filter</a></code> works by introducing indirection into
  +    the filter chain.  Instead of inserting filters in the chain, we insert
  +    a filter harness which in turn dispatches conditionally
  +    to a filter provider.  Any content filter may be used as a provider
  +    to <code class="module"><a href="../mod/mod_filter.html">mod_filter</a></code>; no change to existing filter modules
  +    is required (although it may be possible to simplify them).  There can be
  +    multiple providers for one filter, but no more than one provider will
  +    run for any single request.</p>
  +
  +    <p>A filter chain comprises any number of instances of the filter
  +    harness, each of which may have any number of providers.  A special
  +    case is that of a single provider with unconditional dispatch: this
  +    is equivalent to inserting the provider filter directly into the chain.</p>
   </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
   <div class="section">
   <h2><a name="config" id="config">Configuring the Chain</a></h2>
  -<p>There are three stages to configuring a filter chain with mod_filter.
  -For details of the directives, see below.</p>
  -<dl>
  -<dt>Declare Filters</dt>
  -<dd>The <code class="directive">FilterDeclare</code> directive declares a filter,
  -assigning it a name and a dispatch criterion.</dd>
  -<dt>Register Providers</dt>
  -<dd>The <code class="directive">FilterProvider</code> directive registers a provider with a filter.
  -The filter must have been registered with <code class="directive">FilterDeclare</code>.
  -The provider must have been registered with
  -<code>ap_register_output_filter</code> by some module.  The final argument
  -to <code class="directive">FilterProvider</code> is a match string, that will be checked against
  -the filter's dispatch criterion to determine whether to run this provider.</dd>
  -<dt>Configure the Chain</dt>
  -<dd>The above directives build components of a smart filter chain,
  -but do not configure it to run.  The <code class="directive">FilterChain</code> directive
  -builds a filter chain from smart filters declared, offering the
  -flexibility to insert filters at the beginning or end of the chain,
  -remove a filter, or clear the chain.</dd>
  +    <p>There are three stages to configuring a filter chain with
  +    <code class="module"><a href="../mod/mod_filter.html">mod_filter</a></code>. For details of the directives, see below.</p>
  +
  +    <dl>
  +    <dt>Declare Filters</dt>
  +    <dd>The <code class="directive"><a href="#filterdeclare">FilterDeclare</a></code> directive
  +    declares a filter, assigning it a name and a dispatch criterion.</dd>
  +
  +    <dt>Register Providers</dt>
  +    <dd>The <code class="directive"><a href="#filterprovider">FilterProvider</a></code>
  +    directive registers a provider with a filter. The filter must have
  +    been registered with <code class="directive"><a href="#filterdeclare">FilterDeclare</a></code>. The provider must have been
  +    registered with <code>ap_register_output_filter</code> by some module.
  +    The final argument to <code class="directive"><a href="#filterprovider">FilterProvider</a></code> is a match string, that will be checked
  +    against the filter's dispatch criterion to determine whether to run
  +    this provider.</dd>
  +
  +    <dt>Configure the Chain</dt>
  +    <dd>The above directives build components of a smart filter chain,
  +    but do not configure it to run.  The <code class="directive"><a href="#filterchain">FilterChain</a></code> directive builds a filter chain from smart
  +    filters declared, offering the flexibility to insert filters at the
  +    beginning or end of the chain, remove a filter, or clear the chain.</dd>
   </dl>
   </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
   <div class="section">
   <h2><a name="examples" id="examples">Examples</a></h2>
  -<dl>
  -<dt>Serverside Includes (SSI)</dt>
  -<dd>
  -<p>A simple case of using mod_filter in place of
  -<code>AddOutputFilterByType</code></p>
  -<div class="example"><p><code>
  -FilterDeclare SSI Content-Type<br />
  -FilterProvider SSI INCLUDES $text/html<br />
  -FilterChain SSI<br />
  -</code></p></div>
  -</dd>
  -<dt>Serverside Includes (SSI)</dt>
  -<dd>
  -<p>The same as the above but dispatching on handler (classic
  -SSI behaviour; .shtml files get processed).</p>
  -<div class="example"><p><code>
  -FilterDeclare SSI Handler<br />
  -FilterProvider SSI INCLUDES server-parsed<br />
  -FilterChain SSI<br />
  -</code></p></div>
  -</dd>
  -<dt>Emulating mod_gzip with mod_deflate</dt>
  -<dd>
  -<p>Insert INFLATE filter only if "gzip" is NOT in the
  -Accept-Encoding header.</p>
  -<div class="example"><p><code>
  -FilterDeclare gzip req=Accept-Encoding<br />
  -FilterProvider gzip inflate !$gzip<br />
  -FilterChain gzip<br />
  -</code></p></div>
  -</dd>
  -<dt>Image Downsampling</dt>
  -<dd>
  -<p>Suppose we want to downsample all web images, and have filters
  -for GIF, JPEG and PNG.</p>
  -<div class="example"><p><code>
  -FilterDeclare unpack Content-Type<br />
  -FilterProvider unpack jpeg_unpack $image/jpeg<br />
  -FilterProvider unpack gif_unpack $image/gif<br />
  -FilterProvider unpack png_unpack $image/png<br />
  -FilterDeclare downsample Content-Type<br />
  -FilterProvider downsample downsample_filter $image<br />
  -FilterProtocol downsample "change=yes"<br />
  -FilterDeclare repack Content-Type<br />
  -FilterProvider repack jpeg_pack $image/jpeg<br />
  -FilterProvider repack gif_pack $image/gif<br />
  -FilterProvider repack png_pack $image/png<br />
  -&lt;Location /image-filter&gt;<br />
  -FilterChain unpack downsample repack<br />
  -&lt;/Location&gt;
  -</code></p></div>
  -</dd>
  -</dl>
  +    <dl>
  +    <dt>Server side Includes (SSI)</dt>
  +    <dd>A simple case of using <code class="module"><a href="../mod/mod_filter.html">mod_filter</a></code> in place of
  +    <code class="directive"><a href="../mod/core.html#addoutputfilterbytype">AddOutputFilterByType</a></code>
  +    <div class="example"><p><code>
  +      FilterDeclare SSI Content-Type<br />
  +      FilterProvider SSI INCLUDES $text/html<br />
  +      FilterChain SSI
  +    </code></p></div>
  +    </dd>
  +
  +    <dt>Server side Includes (SSI)</dt>
  +    <dd>The same as the above but dispatching on handler (classic
  +    SSI behaviour; .shtml files get processed).
  +    <div class="example"><p><code>
  +      FilterDeclare SSI Handler<br />
  +      FilterProvider SSI INCLUDES server-parsed<br />
  +      FilterChain SSI
  +    </code></p></div>
  +    </dd>
  +
  +    <dt>Emulating mod_gzip with mod_deflate</dt>
  +    <dd>Insert INFLATE filter only if "gzip" is NOT in the
  +    Accept-Encoding header.
  +    <div class="example"><p><code>
  +      FilterDeclare gzip req=Accept-Encoding<br />
  +      FilterProvider gzip inflate !$gzip<br />
  +      FilterChain gzip
  +    </code></p></div>
  +    </dd>
  +
  +    <dt>Image Downsampling</dt>
  +    <dd>Suppose we want to downsample all web images, and have filters
  +    for GIF, JPEG and PNG.
  +    <div class="example"><p><code>
  +      FilterDeclare unpack Content-Type<br />
  +      FilterProvider unpack jpeg_unpack $image/jpeg<br />
  +      FilterProvider unpack gif_unpack $image/gif<br />
  +      FilterProvider unpack png_unpack $image/png<br />
  +      <br />
  +      FilterDeclare downsample Content-Type<br />
  +      FilterProvider downsample downsample_filter $image<br />
  +      FilterProtocol downsample "change=yes"<br />
  +      <br />
  +      FilterDeclare repack Content-Type<br />
  +      FilterProvider repack jpeg_pack $image/jpeg<br />
  +      FilterProvider repack gif_pack $image/gif<br />
  +      FilterProvider repack png_pack $image/png<br />
  +      &lt;Location /image-filter&gt;<br />
  +      <span class="indent">
  +        FilterChain unpack downsample repack<br />
  +      </span>
  +      &lt;/Location&gt;
  +    </code></p></div>
  +    </dd>
  +    </dl>
   </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
   <div class="section">
   <h2><a name="protocol" id="protocol">Protocol Handling</a></h2>
  -<p>Historically, each filter is responsible for ensuring that whatever
  -changes it makes are correctly represented in the HTTP response headers,
  -and that it does not run when it would make an illegal change.  This
  -imposes a burden on filter authors to re-implement some common
  -functionality in every filter:</p>
  -<ul>
  -<li>Many filters will change the content, invalidating existing content
  -tags, checksums, hashes, and lengths.</li>
  -<li>Filters that require an entire, unbroken response in input need to
  -ensure they don't get byteranges from a backend.</li>
  -<li>Filters that transform output in a filter need to ensure they don't
  -violate a <code>Cache-Control: no-transform</code> header from the
  -backend.</li>
  -<li>Filters may make responses uncacheable.</li>
  -</ul>
  -<p>mod_filter aims to offer generic handling of these details of filter
  -implementation, reducing the complexity required of content filter modules.
  -This is work-in-progress; the <code class="directive">FilterProtocol</code>
  -implements some of this functionality, but there are no API calls yet.</p>
  -<p>At the same time, mod_filter should not interfere with a filter that
  -wants to handle all aspects of the protocol.  By default (i.e. in the
  -absence of any <code class="directive">FilterProtocol</code> directives), mod_filter
  -will leave the headers untouched.</p>
  +    <p>Historically, each filter is responsible for ensuring that whatever
  +    changes it makes are correctly represented in the HTTP response headers,
  +    and that it does not run when it would make an illegal change.  This
  +    imposes a burden on filter authors to re-implement some common
  +    functionality in every filter:</p>
  +
  +    <ul>
  +    <li>Many filters will change the content, invalidating existing content
  +    tags, checksums, hashes, and lengths.</li>
  +
  +    <li>Filters that require an entire, unbroken response in input need to
  +    ensure they don't get byteranges from a backend.</li>
  +
  +    <li>Filters that transform output in a filter need to ensure they don't
  +    violate a <code>Cache-Control: no-transform</code> header from the
  +    backend.</li>
  +
  +    <li>Filters may make responses uncacheable.</li>
  +    </ul>
  +
  +    <p><code class="module"><a href="../mod/mod_filter.html">mod_filter</a></code> aims to offer generic handling of these
  +    details of filter implementation, reducing the complexity required of
  +    content filter modules. This is work-in-progress; the
  +    <code class="directive"><a href="#filterprotocol">FilterProtocol</a></code> implements
  +    some of this functionality, but there are no API calls yet.</p>
  +
  +    <p>At the same time, <code class="module"><a href="../mod/mod_filter.html">mod_filter</a></code> should not interfere
  +    with a filter that wants to handle all aspects of the protocol.  By
  +    default (i.e. in the absence of any <code class="directive"><a href="#filterprotocol">FilterProtocol</a></code> directives), <code class="module"><a href="../mod/mod_filter.html">mod_filter</a></code>
  +    will leave the headers untouched.</p>
   </div>
   <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
   <div class="directive-section"><h2><a name="FilterChain" id="FilterChain">FilterChain</a> <a name="filterchain" id="filterchain">Directive</a></h2>
   <table class="directive">
   <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Configure the filter chain</td></tr>
  -<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>FilterChain ([+=-@!]<var>filter-name</var>)+</code></td></tr>
  +<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>FilterChain [+=-@!]<var>filter-name</var> <var>...</var></code></td></tr>
   <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
   <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
   <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_filter</td></tr>
   </table>
  -<p>This configures an actual filter chain, from declared filters.
  -<code class="directive">FilterChain</code> takes any number of arguments,
  -each optionally preceded with a single-character control that
  -determines what to do:</p>
  -<dl>
  -<dt>+filter-name</dt>
  -<dd>Add filter-name to the end of the filter chain</dd>
  -<dt>@filter-name</dt>
  -<dd>Insert filter-name at the start of the filter chain</dd>
  -<dt>-filter-name</dt>
  -<dd>Remove filter-name from the filter chain</dd>
  -<dt>=filter-name</dt>
  -<dd>Empty the filter chain and insert filter-name</dd>
  -<dt>!</dt>
  -<dd>Empty the filter chain</dd>
  -<dt>filter-name</dt>
  -<dd>Equivalent to +filter-name</dd>
  -</dl>
  +    <p>This configures an actual filter chain, from declared filters.
  +    <code class="directive">FilterChain</code> takes any number of arguments,
  +    each optionally preceded with a single-character control that
  +    determines what to do:</p>
  +
  +    <dl>
  +    <dt><code>+<var>filter-name</var></code></dt>
  +    <dd>Add <var>filter-name</var> to the end of the filter chain</dd>
  +
  +    <dt><code>@<var>filter-name</var></code></dt>
  +    <dd>Insert <var>filter-name</var> at the start of the filter chain</dd>
  +
  +    <dt><code>-<var>filter-name</var></code></dt>
  +    <dd>Remove <var>filter-name</var> from the filter chain</dd>
  +
  +    <dt><code>=<var>filter-name</var></code></dt>
  +    <dd>Empty the filter chain and insert <var>filter-name</var></dd>
  +
  +    <dt><code>!</code></dt>
  +    <dd>Empty the filter chain</dd>
  +
  +    <dt><code><var>filter-name</var></code></dt>
  +    <dd>Equivalent to <code>+<var>filter-name</var></code></dd>
  +    </dl>
   
   </div>
   <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
  @@ -246,141 +265,159 @@
   <table class="directive">
   <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Declare a smart filter</td></tr>
   <tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>FilterDeclare <var>filter-name</var> [req|resp|env]=<var>dispatch</var>
  -<var>[type]</var>
  -</code></td></tr>
  +    <var>[type]</var></code></td></tr>
   <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
   <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
   <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_filter</td></tr>
   </table>
  -<p>This directive declares an output filter together with a
  -header or environment variable that will determine runtime
  -configuration.  The first argument is a <code>filter-name</code>
  -for use in <code class="directive">FilterProvider</code>,
  -<code class="directive">FilterChain</code> and
  -<code class="directive">FilterProtocol</code> directives.</p>
  -<p>The second is a string with optional <code>req=</code>,
  -<code>resp=</code> or <code>env=</code> prefix causing it
  -to dispatch on (respectively) the request header, response
  -header, or environment variable named.  In the absence of a
  -prefix, it defaults to a response header.  A special case is the
  -word "handler", which causes mod_filter to dispatch on the handler.</p>
  -<p>The final (optional) argument
  -is the type of filter, and takes values of <var>ap_filter_type</var>
  -- namely <var>RESOURCE</var> (the default), <var>CONTENT_SET</var>,
  -<var>PROTOCOL</var>, <var>TRANSCODE</var>, <var>CONNECTION</var>
  -or <var>NETWORK</var>.
  -</p>
  +    <p>This directive declares an output filter together with a
  +    header or environment variable that will determine runtime
  +    configuration.  The first argument is a <var>filter-name</var>
  +    for use in <code class="directive"><a href="#filterprovider">FilterProvider</a></code>,
  +    <code class="directive"><a href="#filterchain">FilterChain</a></code> and
  +    <code class="directive"><a href="#filterprotocol">FilterProtocol</a></code> directives.</p>
  +
  +    <p>The second is a string with optional <code>req=</code>,
  +    <code>resp=</code> or <code>env=</code> prefix causing it
  +    to dispatch on (respectively) the request header, response
  +    header, or environment variable named.  In the absence of a
  +    prefix, it defaults to a response header.  A special case is the
  +    word <code>handler</code>, which causes <code class="module"><a href="../mod/mod_filter.html">mod_filter</a></code>
  +    to dispatch on the content handler.</p>
   
  +    <p>The final (optional) argument
  +    is the type of filter, and takes values of <code>ap_filter_type</code>
  +    - namely <code>RESOURCE</code> (the default), <code>CONTENT_SET</code>,
  +    <code>PROTOCOL</code>, <code>TRANSCODE</code>, <code>CONNECTION</code>
  +    or <code>NETWORK</code>.</p>
   
   </div>
   <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
   <div class="directive-section"><h2><a name="FilterProtocol" id="FilterProtocol">FilterProtocol</a> <a name="filterprotocol" id="filterprotocol">Directive</a></h2>
   <table class="directive">
   <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Deal with correct HTTP protocol handling</td></tr>
  -<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>FilterProtocol filter-name [provider-name] "proto-flags"</code></td></tr>
  +<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>FilterProtocol <var>filter-name</var> [<var>provider-name</var>]
  +    <var>proto-flags</var></code></td></tr>
   <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
   <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
   <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_filter</td></tr>
   </table>
  -<p>This directs mod_filter to deal with ensuring the filter doesn't run
  -when it shouldn't, and that the HTTP response headers are correctly set
  -taking into account the effects of the filter.</p>
  -<p>There are two forms of this directive.  With three arguments, it
  -applies specifically to a filter-name and a provider for that filter.
  -With two arguments it applies to a filter-name whenever the filter runs
  -<em>any</em> provider.</p>
  -<p>proto-flags is one or more of</p>
  -<dl>
  -<dt>change=yes</dt>
  -<dd>The filter changes the content, including possibly the content length</dd>
  -<dt>change=1:1</dt>
  -<dd>The filter changes the content, but will not change the content length</dd>
  -<dt>byteranges=no</dt>
  -<dd>The filter cannot work on byteranges and requires complete input</dd>
  -<dt>proxy=no</dt>
  -<dd>The filter should not run in a proxy context</dd>
  -<dt>proxy=transform</dt>
  -<dd>The filter transforms the response in a manner incompatible with
  -the HTTP <code>Cache-Control: no-transform</code> header.</dd>
  -<dt>cache=no</dt>
  -<dd>The filter renders the output uncacheable (eg by introducing randomised
  -content changes)</dd>
  -</dl>
  +    <p>This directs <code class="module"><a href="../mod/mod_filter.html">mod_filter</a></code> to deal with ensuring the
  +    filter doesn't run when it shouldn't, and that the HTTP response
  +    headers are correctly set taking into account the effects of the
  +    filter.</p>
  +
  +    <p>There are two forms of this directive.  With three arguments, it
  +    applies specifically to a <var>filter-name</var> and a
  +    <var>provider-name</var> for that filter.
  +    With two arguments it applies to a <var>filter-name</var> whenever the
  +    filter runs <em>any</em> provider.</p>
  +
  +    <p><var>proto-flags</var> is one or more of</p>
  +
  +    <dl>
  +    <dt><code>change=yes</code></dt>
  +    <dd>The filter changes the content, including possibly the content
  +    length</dd>
  +
  +    <dt><code>change=1:1</code></dt>
  +    <dd>The filter changes the content, but will not change the content
  +    length</dd>
  +
  +    <dt><code>byteranges=no</code></dt>
  +    <dd>The filter cannot work on byteranges and requires complete input</dd>
  +
  +    <dt><code>proxy=no</code></dt>
  +    <dd>The filter should not run in a proxy context</dd>
  +
  +    <dt><code>proxy=transform</code></dt>
  +    <dd>The filter transforms the response in a manner incompatible with
  +    the HTTP <code>Cache-Control: no-transform</code> header.</dd>
  +
  +    <dt><code>cache=no</code></dt>
  +    <dd>The filter renders the output uncacheable (eg by introducing randomised
  +    content changes)</dd>
  +    </dl>
   
   </div>
   <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
   <div class="directive-section"><h2><a name="FilterProvider" id="FilterProvider">FilterProvider</a> <a name="filterprovider" id="filterprovider">Directive</a></h2>
   <table class="directive">
   <tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Register a content filter</td></tr>
  -<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>FilterProvider <var>filter-name</var> <var>provider-name</var> <var>match</var></code></td></tr>
  +<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>FilterProvider <var>filter-name</var> <var>provider-name</var>
  +    <var>match</var></code></td></tr>
   <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
   <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
   <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_filter</td></tr>
   </table>
  -<p>This directive registers a <em>provider</em> for the smart filter.
  -The provider will be called if and only if the <var>match</var> declared
  -here matches the value of the header or environment variable declared
  -as <var>dispatch</var> in the <code class="directive">FilterDeclare</code>
  -directive that declared <var>filter-name</var>.</p>
  -<p><var>filter-name</var> must have been declared with 
  -<code class="directive">FilterDeclare</code>.  <var>provider-name</var> must have
  -been registered by loading a module that registers the name with
  -<code>ap_register_output_filter</code>.</p>
  -<p>The <var>match</var> argument specifies a match that will be applied to
  -the filter's <var>dispatch</var> criterion.  The match may be a string
  -match (exact match or substring), a regexp, an integer (greater, lessthan
  -or equals), or unconditional.  The first characters of the <var>match</var>
  -argument determines this:</p>
  -<p><strong>First</strong>, if the first character is an exclamation mark
  -<strong>!</strong>, this reverses the rule, so the provider will be used
  -if and only if the match <em>fails</em>.</p>
  -<p><strong>Second</strong>, it interprets the first character excluding
  -any leading ! as follows:</p>
  -<dl>
  -<dt>default</dt>
  -<dd>exact match</dd>
  -<dt>$</dt>
  -<dd>substring match</dd>
  -<dt>/</dt>
  -<dd>regexp match</dd>
  -<dt>=</dt>
  -<dd>integer equality</dd>
  -<dt>&lt;</dt>
  -<dd>integer less-than</dd>
  -<dt>&gt;</dt>
  -<dd>integer greater-than</dd>
  -<dt>*</dt>
  -<dd>Unconditional match</dd>
  -</dl>
  +    <p>This directive registers a <em>provider</em> for the smart filter.
  +    The provider will be called if and only if the <var>match</var> declared
  +    here matches the value of the header or environment variable declared
  +    as <var>dispatch</var> in the <code class="directive"><a href="#filterdeclare">FilterDeclare</a></code> directive that declared
  +    <var>filter-name</var>.</p>
  +
  +    <p><var>filter-name</var> must have been declared with
  +    <code class="directive"><a href="#filterdeclare">FilterDeclare</a></code>.
  +    <var>provider-name</var> must have been registered by loading
  +    a module that registers the name with
  +    <code>ap_register_output_filter</code>.</p>
  +
  +    <p>The <var>match</var> argument specifies a match that will be applied to
  +    the filter's <var>dispatch</var> criterion.  The <var>match</var> may be
  +    a string match (exact match or substring), a regexp, an integer (greater,
  +    lessthan or equals), or unconditional.  The first characters of the
  +    <var>match</var> argument determines this:</p>
  +
  +    <p><strong>First</strong>, if the first character is an exclamation mark
  +    (<code>!</code>), this reverses the rule, so the provider will be used
  +    if and only if the match <em>fails</em>.</p>
  +
  +    <p><strong>Second</strong>, it interprets the first character excluding
  +    any leading <code>!</code> as follows:</p>
  +
  +    <table class="bordered"><tr class="header"><th>Character</th><th>Description</th></tr>
  +<tr><td><em>(none)</em></td><td>exact match</td></tr>
  +<tr class="odd"><td><code>$</code></td><td>substring match</td></tr>
  +<tr><td><code>/</code></td><td>regexp match</td></tr>
  +<tr class="odd"><td><code>=</code></td><td>integer equality</td></tr>
  +<tr><td><code>&lt;</code></td><td>integer less-than</td></tr>
  +<tr class="odd"><td><code>&gt;</code></td><td>integer greater-than</td></tr>
  +<tr><td><code>*</code></td><td>Unconditional match</td></tr>
  +</table>
   
   </div>
   <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
   <div class="directive-section"><h2><a name="FilterTrace" id="FilterTrace">FilterTrace</a> <a name="filtertrace" id="filtertrace">Directive</a></h2>
   <table class="directive">
  -<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Get debug/diagnostic information from mod_filter</td></tr>
  -<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>FilterTrace filter-name level</code></td></tr>
  +<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Get debug/diagnostic information from
  +    mod_filter</td></tr>
  +<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>FilterTrace <var>filter-name</var> <var>level</var></code></td></tr>
   <tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
   <tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
   <tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_filter</td></tr>
   </table>
  -<p>This directive generates debug information from mod_filter.
  -It is designed to help test and debug providers (filter modules), although
  -it may also help with mod_filter itself.</p>
  -<p>The debug output depends on the level set:</p>
  -<dl>
  -<dt>0 (default)</dt>
  -<dd>No debug information is generated.</dd>
  -<dt>1</dt>
  -<dd>mod_filter will record buckets and brigades passing through the filter
  -to the error log, before the provider has processed them.
  -This is similar to the information generated by
  -<a href="http://apache.webthing.com/mod_diagnostics/">mod_diagnostics</a>.
  -</dd>
  -<dt>2 (not yet implemented)</dt>
  -<dd>Will dump the full data passing through to a tempfile before the provider.
  -<strong>For single-user debug only</strong>; this will not
  -support concurrent hits.</dd>
  -</dl>
  +    <p>This directive generates debug information from
  +    <code class="module"><a href="../mod/mod_filter.html">mod_filter</a></code>.
  +    It is designed to help test and debug providers (filter modules), although
  +    it may also help with <code class="module"><a href="../mod/mod_filter.html">mod_filter</a></code> itself.</p>
  +
  +    <p>The debug output depends on the <var>level</var> set:</p>
  +    <dl>
  +    <dt><code>0</code> (default)</dt>
  +    <dd>No debug information is generated.</dd>
  +
  +    <dt><code>1</code></dt>
  +    <dd><code class="module"><a href="../mod/mod_filter.html">mod_filter</a></code> will record buckets and brigades
  +    passing through the filter to the error log, before the provider has
  +    processed them. This is similar to the information generated by
  +    <a href="http://apache.webthing.com/mod_diagnostics/">mod_diagnostics</a>.
  +    </dd>
  +
  +    <dt><code>2</code> (not yet implemented)</dt>
  +    <dd>Will dump the full data passing through to a tempfile before the
  +    provider. <strong>For single-user debug only</strong>; this will not
  +    support concurrent hits.</dd>
  +    </dl>
   
   </div>
   </div>
  
  
  
  1.76      +8 -6      httpd-2.0/docs/manual/mod/quickreference.html.de
  
  Index: quickreference.html.de
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/quickreference.html.de,v
  retrieving revision 1.75
  retrieving revision 1.76
  diff -u -u -r1.75 -r1.76
  --- quickreference.html.de	15 Oct 2004 21:21:45 -0000	1.75
  +++ quickreference.html.de	15 Oct 2004 22:48:44 -0000	1.76
  @@ -325,13 +325,15 @@
   beziehen</td></tr>
   <tr><td><a href="core.html#filesmatch">&lt;FilesMatch <var>regex</var>&gt; ... &lt;/FilesMatch&gt;</a></td><td></td><td>svdh</td><td>C</td></tr><tr><td class="descr" colspan="4">Enthlt Direktiven, die fr Dateinamen gelten, die
     auf einen regulren Ausdruck passen</td></tr>
  -<tr class="odd"><td><a href="mod_filter.html#filterchain">FilterChain ([+=-@!]<var>filter-name</var>)+</a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Configure the filter chain</td></tr>
  +<tr class="odd"><td><a href="mod_filter.html#filterchain">FilterChain [+=-@!]<var>filter-name</var> <var>...</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Configure the filter chain</td></tr>
   <tr><td><a href="mod_filter.html#filterdeclare">FilterDeclare <var>filter-name</var> [req|resp|env]=<var>dispatch</var>
  -<var>[type]</var>
  -</a></td><td></td><td>svdh</td><td>E</td></tr><tr><td class="descr" colspan="4">Declare a smart filter</td></tr>
  -<tr class="odd"><td><a href="mod_filter.html#filterprotocol">FilterProtocol filter-name [provider-name] "proto-flags"</a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Deal with correct HTTP protocol handling</td></tr>
  -<tr><td><a href="mod_filter.html#filterprovider">FilterProvider <var>filter-name</var> <var>provider-name</var> <var>match</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr><td class="descr" colspan="4">Register a content filter</td></tr>
  -<tr class="odd"><td><a href="mod_filter.html#filtertrace">FilterTrace filter-name level</a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Get debug/diagnostic information from mod_filter</td></tr>
  +    <var>[type]</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr><td class="descr" colspan="4">Declare a smart filter</td></tr>
  +<tr class="odd"><td><a href="mod_filter.html#filterprotocol">FilterProtocol <var>filter-name</var> [<var>provider-name</var>]
  +    <var>proto-flags</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Deal with correct HTTP protocol handling</td></tr>
  +<tr><td><a href="mod_filter.html#filterprovider">FilterProvider <var>filter-name</var> <var>provider-name</var>
  +    <var>match</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr><td class="descr" colspan="4">Register a content filter</td></tr>
  +<tr class="odd"><td><a href="mod_filter.html#filtertrace">FilterTrace <var>filter-name</var> <var>level</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Get debug/diagnostic information from
  +    <code class="module"><a href="../mod/mod_filter.html">mod_filter</a></code></td></tr>
   <tr><td><a href="mod_negotiation.html#forcelanguagepriority">ForceLanguagePriority None|Prefer|Fallback [Prefer|Fallback]</a></td><td> Prefer </td><td>svdh</td><td>B</td></tr><tr><td class="descr" colspan="4">Action to take if a single acceptable document is not 
   found</td></tr>
   <tr class="odd"><td><a href="core.html#forcetype">ForceType <var>MIME-Type</var>|None</a></td><td></td><td>dh</td><td>C</td></tr><tr class="odd"><td class="descr" colspan="4">Erzwingt die Auslieferung aller passendenden Dateien mit dem
  
  
  
  1.131     +8 -6      httpd-2.0/docs/manual/mod/quickreference.html.en
  
  Index: quickreference.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/quickreference.html.en,v
  retrieving revision 1.130
  retrieving revision 1.131
  diff -u -u -r1.130 -r1.131
  --- quickreference.html.en	15 Oct 2004 21:21:46 -0000	1.130
  +++ quickreference.html.en	15 Oct 2004 22:48:45 -0000	1.131
  @@ -318,13 +318,15 @@
   filenames</td></tr>
   <tr><td><a href="core.html#filesmatch">&lt;FilesMatch <var>regex</var>&gt; ... &lt;/FilesMatch&gt;</a></td><td></td><td>svdh</td><td>C</td></tr><tr><td class="descr" colspan="4">Contains directives that apply to regular-expression matched
   filenames</td></tr>
  -<tr class="odd"><td><a href="mod_filter.html#filterchain">FilterChain ([+=-@!]<var>filter-name</var>)+</a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Configure the filter chain</td></tr>
  +<tr class="odd"><td><a href="mod_filter.html#filterchain">FilterChain [+=-@!]<var>filter-name</var> <var>...</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Configure the filter chain</td></tr>
   <tr><td><a href="mod_filter.html#filterdeclare">FilterDeclare <var>filter-name</var> [req|resp|env]=<var>dispatch</var>
  -<var>[type]</var>
  -</a></td><td></td><td>svdh</td><td>E</td></tr><tr><td class="descr" colspan="4">Declare a smart filter</td></tr>
  -<tr class="odd"><td><a href="mod_filter.html#filterprotocol">FilterProtocol filter-name [provider-name] "proto-flags"</a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Deal with correct HTTP protocol handling</td></tr>
  -<tr><td><a href="mod_filter.html#filterprovider">FilterProvider <var>filter-name</var> <var>provider-name</var> <var>match</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr><td class="descr" colspan="4">Register a content filter</td></tr>
  -<tr class="odd"><td><a href="mod_filter.html#filtertrace">FilterTrace filter-name level</a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Get debug/diagnostic information from mod_filter</td></tr>
  +    <var>[type]</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr><td class="descr" colspan="4">Declare a smart filter</td></tr>
  +<tr class="odd"><td><a href="mod_filter.html#filterprotocol">FilterProtocol <var>filter-name</var> [<var>provider-name</var>]
  +    <var>proto-flags</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Deal with correct HTTP protocol handling</td></tr>
  +<tr><td><a href="mod_filter.html#filterprovider">FilterProvider <var>filter-name</var> <var>provider-name</var>
  +    <var>match</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr><td class="descr" colspan="4">Register a content filter</td></tr>
  +<tr class="odd"><td><a href="mod_filter.html#filtertrace">FilterTrace <var>filter-name</var> <var>level</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Get debug/diagnostic information from
  +    <code class="module"><a href="../mod/mod_filter.html">mod_filter</a></code></td></tr>
   <tr><td><a href="mod_negotiation.html#forcelanguagepriority">ForceLanguagePriority None|Prefer|Fallback [Prefer|Fallback]</a></td><td> Prefer </td><td>svdh</td><td>B</td></tr><tr><td class="descr" colspan="4">Action to take if a single acceptable document is not 
   found</td></tr>
   <tr class="odd"><td><a href="core.html#forcetype">ForceType <var>MIME-type</var>|None</a></td><td></td><td>dh</td><td>C</td></tr><tr class="odd"><td class="descr" colspan="4">Forces all matching files to be served with the specified
  
  
  
  1.16      +8 -6      httpd-2.0/docs/manual/mod/quickreference.html.es
  
  Index: quickreference.html.es
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/quickreference.html.es,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -u -r1.15 -r1.16
  --- quickreference.html.es	15 Oct 2004 21:21:46 -0000	1.15
  +++ quickreference.html.es	15 Oct 2004 22:48:45 -0000	1.16
  @@ -321,13 +321,15 @@
   filenames</td></tr>
   <tr><td><a href="core.html#filesmatch">&lt;FilesMatch <var>regex</var>&gt; ... &lt;/FilesMatch&gt;</a></td><td></td><td>svdh</td><td>C</td></tr><tr><td class="descr" colspan="4">Contains directives that apply to regular-expression matched
   filenames</td></tr>
  -<tr class="odd"><td><a href="mod_filter.html#filterchain">FilterChain ([+=-@!]<var>filter-name</var>)+</a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Configure the filter chain</td></tr>
  +<tr class="odd"><td><a href="mod_filter.html#filterchain">FilterChain [+=-@!]<var>filter-name</var> <var>...</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Configure the filter chain</td></tr>
   <tr><td><a href="mod_filter.html#filterdeclare">FilterDeclare <var>filter-name</var> [req|resp|env]=<var>dispatch</var>
  -<var>[type]</var>
  -</a></td><td></td><td>svdh</td><td>E</td></tr><tr><td class="descr" colspan="4">Declare a smart filter</td></tr>
  -<tr class="odd"><td><a href="mod_filter.html#filterprotocol">FilterProtocol filter-name [provider-name] "proto-flags"</a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Deal with correct HTTP protocol handling</td></tr>
  -<tr><td><a href="mod_filter.html#filterprovider">FilterProvider <var>filter-name</var> <var>provider-name</var> <var>match</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr><td class="descr" colspan="4">Register a content filter</td></tr>
  -<tr class="odd"><td><a href="mod_filter.html#filtertrace">FilterTrace filter-name level</a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Get debug/diagnostic information from mod_filter</td></tr>
  +    <var>[type]</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr><td class="descr" colspan="4">Declare a smart filter</td></tr>
  +<tr class="odd"><td><a href="mod_filter.html#filterprotocol">FilterProtocol <var>filter-name</var> [<var>provider-name</var>]
  +    <var>proto-flags</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Deal with correct HTTP protocol handling</td></tr>
  +<tr><td><a href="mod_filter.html#filterprovider">FilterProvider <var>filter-name</var> <var>provider-name</var>
  +    <var>match</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr><td class="descr" colspan="4">Register a content filter</td></tr>
  +<tr class="odd"><td><a href="mod_filter.html#filtertrace">FilterTrace <var>filter-name</var> <var>level</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Get debug/diagnostic information from
  +    <code class="module"><a href="../mod/mod_filter.html">mod_filter</a></code></td></tr>
   <tr><td><a href="mod_negotiation.html#forcelanguagepriority">ForceLanguagePriority None|Prefer|Fallback [Prefer|Fallback]</a></td><td> Prefer </td><td>svdh</td><td>B</td></tr><tr><td class="descr" colspan="4">Action to take if a single acceptable document is not 
   found</td></tr>
   <tr class="odd"><td><a href="core.html#forcetype">ForceType <var>MIME-type</var>|None</a></td><td></td><td>dh</td><td>C</td></tr><tr class="odd"><td class="descr" colspan="4">Forces all matching files to be served with the specified
  
  
  
  1.8       +8 -6      httpd-2.0/docs/manual/mod/quickreference.html.ja.euc-jp
  
  Index: quickreference.html.ja.euc-jp
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/quickreference.html.ja.euc-jp,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -u -r1.7 -r1.8
  --- quickreference.html.ja.euc-jp	15 Oct 2004 21:21:46 -0000	1.7
  +++ quickreference.html.ja.euc-jp	15 Oct 2004 22:48:45 -0000	1.8
  @@ -301,13 +301,15 @@
   <tr><td><a href="core.html#files">&lt;Files <var>filename</var>&gt; ... &lt;/Files&gt;</a></td><td></td><td>svdh</td><td>C</td></tr><tr><td class="descr" colspan="4">ޥåե̾ŬѤǥ쥯ƥ֤Ϥ</td></tr>
   <tr class="odd"><td><a href="core.html#filesmatch">&lt;FilesMatch <var>regex</var>&gt; ... &lt;/FilesMatch&gt;</a></td><td></td><td>svdh</td><td>C</td></tr><tr class="odd"><td class="descr" colspan="4">ɽ˥ޥåե̾ŬѤ
   ǥ쥯ƥ֤Ϥ</td></tr>
  -<tr><td><a href="mod_filter.html#filterchain">FilterChain ([+=-@!]<var>filter-name</var>)+</a></td><td></td><td>svdh</td><td>E</td></tr><tr><td class="descr" colspan="4">Configure the filter chain</td></tr>
  +<tr><td><a href="mod_filter.html#filterchain">FilterChain [+=-@!]<var>filter-name</var> <var>...</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr><td class="descr" colspan="4">Configure the filter chain</td></tr>
   <tr class="odd"><td><a href="mod_filter.html#filterdeclare">FilterDeclare <var>filter-name</var> [req|resp|env]=<var>dispatch</var>
  -<var>[type]</var>
  -</a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Declare a smart filter</td></tr>
  -<tr><td><a href="mod_filter.html#filterprotocol">FilterProtocol filter-name [provider-name] "proto-flags"</a></td><td></td><td>svdh</td><td>E</td></tr><tr><td class="descr" colspan="4">Deal with correct HTTP protocol handling</td></tr>
  -<tr class="odd"><td><a href="mod_filter.html#filterprovider">FilterProvider <var>filter-name</var> <var>provider-name</var> <var>match</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Register a content filter</td></tr>
  -<tr><td><a href="mod_filter.html#filtertrace">FilterTrace filter-name level</a></td><td></td><td>svdh</td><td>E</td></tr><tr><td class="descr" colspan="4">Get debug/diagnostic information from mod_filter</td></tr>
  +    <var>[type]</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Declare a smart filter</td></tr>
  +<tr><td><a href="mod_filter.html#filterprotocol">FilterProtocol <var>filter-name</var> [<var>provider-name</var>]
  +    <var>proto-flags</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr><td class="descr" colspan="4">Deal with correct HTTP protocol handling</td></tr>
  +<tr class="odd"><td><a href="mod_filter.html#filterprovider">FilterProvider <var>filter-name</var> <var>provider-name</var>
  +    <var>match</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Register a content filter</td></tr>
  +<tr><td><a href="mod_filter.html#filtertrace">FilterTrace <var>filter-name</var> <var>level</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr><td class="descr" colspan="4">Get debug/diagnostic information from
  +    <code class="module"><a href="../mod/mod_filter.html">mod_filter</a></code></td></tr>
   <tr class="odd"><td><a href="mod_negotiation.html#forcelanguagepriority">ForceLanguagePriority None|Prefer|Fallback [Prefer|Fallback]</a></td><td> Prefer </td><td>svdh</td><td>B</td></tr><tr class="odd"><td class="descr" colspan="4">׵˹礦ñȤΥɥȤĤʤäȤ˹ԤʤȤ
   </td></tr>
   <tr><td><a href="core.html#forcetype">ForceType <var>MIME-type</var>|None</a></td><td></td><td>dh</td><td>C</td></tr><tr><td class="descr" colspan="4">٤ƤΥޥåե뤬 MIME ƥȥפ
  
  
  
  1.17      +8 -6      httpd-2.0/docs/manual/mod/quickreference.html.ko.euc-kr
  
  Index: quickreference.html.ko.euc-kr
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/quickreference.html.ko.euc-kr,v
  retrieving revision 1.16
  retrieving revision 1.17
  diff -u -u -r1.16 -r1.17
  --- quickreference.html.ko.euc-kr	15 Oct 2004 21:21:46 -0000	1.16
  +++ quickreference.html.ko.euc-kr	15 Oct 2004 22:48:45 -0000	1.17
  @@ -277,13 +277,15 @@
   filenames</td></tr>
   <tr><td><a href="core.html#filesmatch">&lt;FilesMatch <var>regex</var>&gt; ... &lt;/FilesMatch&gt;</a></td><td></td><td>svdh</td><td>C</td></tr><tr><td class="descr" colspan="4">Contains directives that apply to regular-expression matched
   filenames</td></tr>
  -<tr class="odd"><td><a href="mod_filter.html#filterchain">FilterChain ([+=-@!]<var>filter-name</var>)+</a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Configure the filter chain</td></tr>
  +<tr class="odd"><td><a href="mod_filter.html#filterchain">FilterChain [+=-@!]<var>filter-name</var> <var>...</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Configure the filter chain</td></tr>
   <tr><td><a href="mod_filter.html#filterdeclare">FilterDeclare <var>filter-name</var> [req|resp|env]=<var>dispatch</var>
  -<var>[type]</var>
  -</a></td><td></td><td>svdh</td><td>E</td></tr><tr><td class="descr" colspan="4">Declare a smart filter</td></tr>
  -<tr class="odd"><td><a href="mod_filter.html#filterprotocol">FilterProtocol filter-name [provider-name] "proto-flags"</a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Deal with correct HTTP protocol handling</td></tr>
  -<tr><td><a href="mod_filter.html#filterprovider">FilterProvider <var>filter-name</var> <var>provider-name</var> <var>match</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr><td class="descr" colspan="4">Register a content filter</td></tr>
  -<tr class="odd"><td><a href="mod_filter.html#filtertrace">FilterTrace filter-name level</a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Get debug/diagnostic information from mod_filter</td></tr>
  +    <var>[type]</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr><td class="descr" colspan="4">Declare a smart filter</td></tr>
  +<tr class="odd"><td><a href="mod_filter.html#filterprotocol">FilterProtocol <var>filter-name</var> [<var>provider-name</var>]
  +    <var>proto-flags</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Deal with correct HTTP protocol handling</td></tr>
  +<tr><td><a href="mod_filter.html#filterprovider">FilterProvider <var>filter-name</var> <var>provider-name</var>
  +    <var>match</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr><td class="descr" colspan="4">Register a content filter</td></tr>
  +<tr class="odd"><td><a href="mod_filter.html#filtertrace">FilterTrace <var>filter-name</var> <var>level</var></a></td><td></td><td>svdh</td><td>E</td></tr><tr class="odd"><td class="descr" colspan="4">Get debug/diagnostic information from
  +    <code class="module"><a href="../mod/mod_filter.html">mod_filter</a></code></td></tr>
   <tr><td><a href="mod_negotiation.html#forcelanguagepriority">ForceLanguagePriority None|Prefer|Fallback [Prefer|Fallback]</a></td><td> Prefer </td><td>svdh</td><td>B</td></tr><tr><td class="descr" colspan="4">Action to take if a single acceptable document is not 
   found</td></tr>
   <tr class="odd"><td><a href="core.html#forcetype">ForceType <var>MIME-type</var>|None</a></td><td></td><td>dh</td><td>C</td></tr><tr class="odd"><td class="descr" colspan="4">Forces all matching files to be served with the specified
  
  
  

Mime
View raw message