From: Eric Covener <covener@apache.org>
Date: Fri, 27 Aug 2010 11:50:20 +0000 (+0000)
Subject: doc updates around why a few directives can't set arbitrary Content-Types for
X-Git-Tag: 2.3.9~529
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=c93da3dfe498e30e427811d4a9a7dc8325d33d99;p=apache

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 b83b998c7e..6f5956b6ae 100644
--- 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 565715126c..e559a3c0d7 100644
--- 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 a433e6749c..c94681ea7e 100644
--- 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>