update xforms

    <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">AddOutputFilterByType</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>

    filters can be inserted based on complex boolean

    <a href="../expr.html">expressions</a> This generalises the limited

    flexibility offered by <code class="directive">AddOutputFilterByType</code>.</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>

<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>

<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Base</td></tr>

<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_filter</td></tr>

<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Available in Apache httpd 2.0.33 and later; deprecated in Apache httpd 2.1 and later</td></tr>

<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Version 2.0.33 and later; had severe limitations before

being moved to <code class="module"><a href="../mod/mod_filter.html">mod_filter</a></code> in version 2.3.7</td></tr>

</table>

    <p>This directive activates a particular output <a href="../filter.html">filter</a> for a request depending on the

    response <a class="glossarylink" href="../glossary.html#media-type" title="see glossary">media-type</a>.  Because of certain

    problems discussed below, this directive is deprecated.  The same

    functionality is available using <code class="module"><a href="../mod/mod_filter.html">mod_filter</a></code>.</p>

    response <a class="glossarylink" href="../glossary.html#media-type" title="see glossary">media-type</a>.</p>

    <p>The following example uses the <code>DEFLATE</code> filter, which

    is provided by <code class="module"><a href="../mod/mod_deflate.html">mod_deflate</a></code>. It will compress all

    </Location>

    </code></p></div>

    <div class="warning"><h3>Note</h3>

      <p>Enabling filters with <code class="directive">AddOutputFilterByType</code>

      may fail partially or completely in some cases. For example, no

      filters are applied if the <a class="glossarylink" href="../glossary.html#media-type" title="see glossary">media-type</a> could not

      be determined.  If you want to make sure that the filters will be

      applied, assign the content type to a resource explicitly; for

      example, with <code class="directive"><a href="../mod/mod_mime.html#addtype">AddType</a></code> or

      <code class="directive"><a href="../mod/core.html#forcetype">ForceType</a></code>. Setting the

      content type within a (non-nph) CGI script is also safe.</p>

    </div>

<h3>See also</h3>

<ul>

certificate files. Upon startup, each client certificate configured will

be examined and a chain of trust will be constructed.

</p>

<div class="warning"><h3>Security warning</h3>

<p>If this directive is enabled, all of the certificates in the file will be

trusted as if they were also in <code class="directive"><a href="#&#10;sslproxycacertificatefile">

SSLProxyCACertificateFile</a></code>.</p>

</div>

<div class="example"><h3>Example</h3><p><code>

SSLProxyMachineCertificateChainFile /usr/local/apache2/conf/ssl.crt/proxyCA.pem

</code></p></div>

      <dd>We now have a general-purpose expression parser, whose API is

          exposed in <var>ap_expr.h</var>.  This is adapted from the

          expression parser previously implemented in

          <code class="module"><a href="./mod/mod_include.html">mod_include</a></code>.</dd>

          <code class="module"><a href="./mod/mod_ssl.html">mod_ssl</a></code>.</dd>

      <dt>Authorization Logic Containers</dt>

      warning.  Any address/port combination appearing in multiple

      virtual hosts is implicitly treated as a name-based virtual host.

      </li>

    </ul>

      <li><code class="module"><a href="./mod/mod_deflate.html">mod_deflate</a></code> will now skip compression if it knows

      that the size overhead added by the compression is larger than the data

      to be compressed.

      </li>

    </ul>

  </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>

<div class="section">

<p><span>Langues Disponibles: </span><a href="./en/upgrading.html" hreflang="en" rel="alternate" title="English">&nbsp;en&nbsp;</a> |

<a href="./fr/upgrading.html" title="Français">&nbsp;fr&nbsp;</a></p>

</div>

<div class="outofdate">Cette traduction peut être périmée. Vérifiez la version

            anglaise pour les changements récents.</div>

  <p>Afin d'assister les utilisateurs lors de leurs opérations de mise à

  jour, nous maintenons un document