You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by nd...@apache.org on 2002/12/08 01:42:12 UTC
cvs commit: httpd-2.0/docs/manual/mod core.html.en core.xml
nd 2002/12/07 16:42:12
Modified: docs/manual/mod core.html.en core.xml
Log:
add some explanations how to use AOFBT correctly.
related to: PR 15045
Reviewed by: Astrid Ke�ler <ke...@kess-net.de>
Revision Changes Path
1.49 +13 -3 httpd-2.0/docs/manual/mod/core.html.en
Index: core.html.en
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/mod/core.html.en,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -r1.48 -r1.49
--- core.html.en 5 Dec 2002 15:18:34 -0000 1.48
+++ core.html.en 8 Dec 2002 00:42:11 -0000 1.49
@@ -222,10 +222,20 @@
</Location>
</code></p></div>
- <div class="note"><h3>Note:</h3>
- <p>The output filters are not applied on proxy requests.</p>
+ <div class="warning"><h3>Note:</h3>
+ <p>Enabling filters with <code class="directive">AddOutputFilterByType</code>
+ may fail partially or completely in some cases. For expample, no
+ filters are applied if the content type falls back to the <code class="directive"><a href="#defaulttype">DefaultType</a></code>, even if the <code class="directive"><a href="#defaulttype">DefaultType</a></code> is the same.</p>
+
+ <p>However, if you want to make sure, that the filters will be
+ applied, assign the content type to a resource explicitely, for
+ example with <code class="directive"><a href="../mod/mod_mime.html#addtype">AddType</a></code> or
+ <code class="directive"><a href="#forcetype">ForceType</a></code>. Setting the
+ content type within a (non-nph) CGI script is also safe.</p>
+
+ <p>The output filters are never applied on proxy requests.</p>
</div>
-<h3>See also</h3><ul><li><code class="directive"><a href="../mod/mod_mime.html#addoutputfilter">AddOutputFilter</a></code></li><li><code class="directive"><a href="#setoutputfilter">SetOutputFilter</a></code></li><li><code class="module"><a href="../mod/mod_include.html">mod_include</a></code></li><li><code class="module"><a href="../mod/mod_deflate.html">mod_deflate</a></code></li><li><a href="../filter.html">The filters documentation</a></li></ul></div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="directive-section"><h2><a name="AllowOverride" id="AllowOverride">AllowOverride</a> <a name="allowoverride" id="allowoverride">Directive</a></h2><table class="directive"><tr><th><a href="directive-dict.html#Description">Description:
+<h3>See also</h3><ul><li><code class="directive"><a href="../mod/mod_mime.html#addoutputfilter">AddOutputFilter</a></code></li><li><code class="directive"><a href="#setoutputfilter">SetOutputFilter</a></code></li><li><a href="../filter.html">filters</a></li></ul></div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="directive-section"><h2><a name="AllowOverride" id="AllowOverride">AllowOverride</a> <a name="allowoverride" id="allowoverride">Directive</a></h2><table class="directive"><tr><th><a href="directive-dict.html#Description">Description:
</a></th><td>Types of directives that are allowed in
.htaccess files</td></tr><tr><th><a href="directive-dict.html#Syntax">Syntax:
</a></th><td><code>AllowOverride All|None|<var>directive-type</var>
1.47 +15 -5 httpd-2.0/docs/manual/mod/core.xml
Index: core.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/mod/core.xml,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -r1.46 -r1.47
--- core.xml 21 Nov 2002 17:42:12 -0000 1.46
+++ core.xml 8 Dec 2002 00:42:11 -0000 1.47
@@ -190,16 +190,26 @@
</Location>
</example>
- <note><title>Note:</title>
- <p>The output filters are not applied on proxy requests.</p>
+ <note type="warning"><title>Note:</title>
+ <p>Enabling filters with <directive>AddOutputFilterByType</directive>
+ may fail partially or completely in some cases. For expample, no
+ filters are applied if the content type falls back to the <directive
+ module="core">DefaultType</directive>, even if the <directive
+ module="core">DefaultType</directive> is the same.</p>
+
+ <p>However, if you want to make sure, that the filters will be
+ applied, assign the content type to a resource explicitely, for
+ example with <directive module="mod_mime">AddType</directive> or
+ <directive module="core">ForceType</directive>. Setting the
+ content type within a (non-nph) CGI script is also safe.</p>
+
+ <p>The output filters are never applied on proxy requests.</p>
</note>
</usage>
<seealso><directive module="mod_mime">AddOutputFilter</directive></seealso>
<seealso><directive module="core">SetOutputFilter</directive></seealso>
-<seealso><module>mod_include</module></seealso>
-<seealso><module>mod_deflate</module></seealso>
-<seealso><a href="../filter.html">The filters documentation</a></seealso>
+<seealso><a href="../filter.html">filters</a></seealso>
</directivesynopsis>
<directivesynopsis>