Added information about how to set the Content-type for

	module-generated content.

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

diff --git a/docs/manual/developer/API.html b/docs/manual/developer/API.html
index 7ff12086aa93a2b0950992854374308d6a3dc172..a45d8694cb5a3451db4dbbddd9a97d88257f72bb 100644 (file)
--- a/docs/manual/developer/API.html
+++ b/docs/manual/developer/API.html
@@ -233,7 +233,16 @@ response (which modules can add to at will), and environment variables
 for any subprocesses which are spawned off in the course of servicing
 the request.  These tables are manipulated using the
 <code>table_get</code> and <code>table_set</code> routines. <p>
-
+<BLOCKQUOTE>
+ Note that the <SAMP>Content-type</SAMP> header value <EM>cannot</EM> be
+ set by module content-handlers using the <SAMP>table_*()</SAMP>
+ routines.  Rather, it is set by pointing the <SAMP>content_type</SAMP>
+ field in the <SAMP>request_rec</SAMP> structure to an appropriate
+ string.  <EM>E.g.</EM>,
+ <PRE>
+  r-&gt;content_type = "text/html";
+ </PRE>
+</BLOCKQUOTE>
 Finally, there are pointers to two data structures which, in turn,
 point to per-module configuration structures.  Specifically, these
 hold pointers to the data structures which the module has built to

diff --git a/docs/manual/misc/API.html b/docs/manual/misc/API.html
index 7ff12086aa93a2b0950992854374308d6a3dc172..a45d8694cb5a3451db4dbbddd9a97d88257f72bb 100644 (file)
--- a/docs/manual/misc/API.html
+++ b/docs/manual/misc/API.html
@@ -233,7 +233,16 @@ response (which modules can add to at will), and environment variables
 for any subprocesses which are spawned off in the course of servicing
 the request.  These tables are manipulated using the
 <code>table_get</code> and <code>table_set</code> routines. <p>
-
+<BLOCKQUOTE>
+ Note that the <SAMP>Content-type</SAMP> header value <EM>cannot</EM> be
+ set by module content-handlers using the <SAMP>table_*()</SAMP>
+ routines.  Rather, it is set by pointing the <SAMP>content_type</SAMP>
+ field in the <SAMP>request_rec</SAMP> structure to an appropriate
+ string.  <EM>E.g.</EM>,
+ <PRE>
+  r-&gt;content_type = "text/html";
+ </PRE>
+</BLOCKQUOTE>
 Finally, there are pointers to two data structures which, in turn,
 point to per-module configuration structures.  Specifically, these
 hold pointers to the data structures which the module has built to