Update SSI docs to use AddOutputFilter in place of SetOutputFilter.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@92349 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/howto/ssi.html.en b/docs/manual/howto/ssi.html.en
index 812f0c683b4d0dfb6321cb22af7489b07e7277d6..eef2ed2f9f1930021283b6355948dcab84e5431b 100644 (file)
--- a/docs/manual/howto/ssi.html.en
+++ b/docs/manual/howto/ssi.html.en
@@ -160,9 +160,7 @@
     the following directives:</p>
 <pre>
         AddType text/html .shtml
-        &lt;FilesMatch "\.shtml(\..+)?$"&gt;
-          SetOutputFilter INCLUDES
-        &lt;/FilesMatch&gt;
+       AddOutputFilter INCLUDES .shtml
 </pre>
 
     <p>One disadvantage to this approach is that if you wanted to

diff --git a/docs/manual/mod/mod_include.html b/docs/manual/mod/mod_include.html
index 8d9623cb4694ac4e5f15435f98a6fb76fd953361..5a309c4db07cadcba49e8173c08004b78cfda180 100644 (file)
--- a/docs/manual/mod/mod_include.html
+++ b/docs/manual/mod/mod_include.html
@@ -55,22 +55,9 @@
 
     <blockquote>
       <code>AddType text/html .shtml<br />
-       &lt;FilesMatch "\.shtml(\..+)?$"&gt;<br />
-       &nbsp;&nbsp;SetOutputFilter INCLUDES<br />
-       &lt;/FilesMatch&gt;</code>
+            AddOutputFilter INCLUDES .shtml</code>
     </blockquote>
 
-    <p>Be careful to properly scope the INCLUDES filter to process
-    only the correct files. The filter is <strong>not</strong>
-    restricted to processing only HTML files. So, for example, if
-    the INCLUDES filter is activated using a
-    <code>&lt;Directory&gt;</code> section and that directory
-    includes GIF files, mod_include will process the GIF files.
-    This can have two adverse consequences: 1. there will be extra
-    overhead in serving these files, and 2. these files could
-    become corrupted if they happen to contain something that looks
-    like an SSI element.</p>
-
     <p>The following directive must be given for the directories
     containing the shtml files (typically in a
     <code>&lt;Directory&gt;</code> section, but this directive is