Ya know, the language here wasn't all that explicit. We are testing for

  content-type text/html, so we better spell that out up front.

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

diff --git a/docs/manual/mod/mod_include.html b/docs/manual/mod/mod_include.html
index 5a309c4db07cadcba49e8173c08004b78cfda180..75497ab2374d47c948dbf4af4b4b71c56c4abf69 100644 (file)
--- a/docs/manual/mod/mod_include.html
+++ b/docs/manual/mod/mod_include.html
@@ -509,8 +509,8 @@
 
       <dt>on</dt>
 
-      <dd>Any file that has the user-execute bit set will be
-      treated as a server-parsed html document.</dd>
+      <dd>Any text/html file that has the user-execute bit set will 
+      be treated as a server-parsed html document.</dd>
 
       <dt>full</dt>
 
@@ -522,10 +522,11 @@
         this bit allows clients and proxies to cache the result of
         the request. 
 
-        <p><strong>Note:</strong> you would not want to use this,
-        for example, when you <code>#include</code> a CGI that
-        produces different output on each hit (or potentially
-        depends on the hit).</p>
+        <p><strong>Note:</strong> you would not want to use the full
+        option, unless you assure the group-execute bit is unset for
+        every SSI script which might <code>#include</code> a CGI 
+        or otherwise produces different output on each hit (or could 
+        potentially change on subsequent requests).</p>
       </dd>
     </dl>