From: Nick Kew <niq@apache.org>
Date: Tue, 21 Feb 2006 21:19:37 +0000 (+0000)
Subject: Fix mod_asis docs re: use of HTTP/CGI headers.
X-Git-Tag: 2.0.56~48
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=1282455f36280e8a7d7f0cb403a439b8b2093291;p=thirdparty%2Fapache%2Fhttpd.git

Fix mod_asis docs re: use of HTTP/CGI headers.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x@379591 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/mod/mod_asis.xml b/docs/manual/mod/mod_asis.xml
index 2f8fbd3ceb5..a8e81bb2e23 100644
--- a/docs/manual/mod/mod_asis.xml
+++ b/docs/manual/mod/mod_asis.xml
@@ -55,10 +55,11 @@ HTTP headers</description>
 
     <p>The contents of any file with a <code>.asis</code> extension
     will then be sent by Apache to the client with almost no
-    changes. Clients will need HTTP headers to be attached, so do
-    not forget them. A Status: header is also required; the data
-    should be the 3-digit HTTP response code, followed by a textual
-    message.</p>
+    changes. In particular, HTTP headers are derived from the file
+    itself according to <module>mod_cgi</module> rules, so an asis
+    file must include valid headers, and may also use the CGI
+    Status: header to determine the HTTP response code.</p>
+
 
     <p>Here's an example of a file whose contents are sent <em>as
     is</em> so as to tell the client that a file has