doc updates around why a few directives can't set arbitrary Content-Types for

non-static responses.

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

diff --git a/docs/manual/mod/core.xml b/docs/manual/mod/core.xml
index b83b998c7ea803951fdf9f35b47e457ebd6b18ee..6f5956b6ae341a714a902d631816157e4bb5577b 100644 (file)
--- a/docs/manual/mod/core.xml
+++ b/docs/manual/mod/core.xml
@@ -1276,6 +1276,12 @@ media type in the HTTP Content-Type header field</description>
       </indent>
       &lt;/Location&gt;
     </example>
+
+    <p>This directive primarily overrides the content types generated for
+    static files served out of the filesystem.  For resources other than 
+    static files, where the generator of the response typically specifies 
+    a Content-Type, this directive has no effect.</p>
+
 </usage>
 </directivesynopsis>
 

diff --git a/docs/manual/mod/mod_headers.xml b/docs/manual/mod/mod_headers.xml
index 565715126c8d0f86e0ec5ac5ec289b76436b2208..e559a3c0d732c204eb9f798215d46efb983036d2 100644 (file)
--- a/docs/manual/mod/mod_headers.xml
+++ b/docs/manual/mod/mod_headers.xml
@@ -447,7 +447,7 @@ headers</description>
     <directive>Header</directive> directives are processed just
     before the response is sent to the network. These means that it is
     possible to set and/or override most headers, except for those headers
-    added by the header filter.</p>
+    added by the HTTP header filter, such as Content-Type.</p>
 </usage>
 </directivesynopsis>
 

diff --git a/docs/manual/mod/mod_mime.xml b/docs/manual/mod/mod_mime.xml
index a433e6749c2d3d553cdb878a2cb6798541ee3b02..c94681ea7e18b90742037b3e85c50a7178fee5a7 100644 (file)
--- a/docs/manual/mod/mod_mime.xml
+++ b/docs/manual/mod/mod_mime.xml
@@ -554,6 +554,12 @@ type</description>
     href="#multipleext">multiple extensions</a> and the
     <var>extension</var> argument will be compared against each of
     them.</p>
+
+    <p>This directive primarily configures the content types generated for
+    static files served out of the filesystem.  For resources other than 
+    static files, where the generator of the response typically specifies 
+    a Content-Type, this directive has no effect.</p>
+
 </usage>
 <seealso><directive module="core">ForceType</directive></seealso>
 </directivesynopsis>