You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by ni...@apache.org on 2006/02/21 22:19:41 UTC
svn commit: r379591 - in /httpd/httpd:
branches/2.0.x/docs/manual/mod/mod_asis.xml
branches/2.2.x/docs/manual/mod/mod_asis.xml
trunk/docs/manual/mod/mod_asis.xml
Author: niq
Date: Tue Feb 21 13:19:37 2006
New Revision: 379591
URL: http://svn.apache.org/viewcvs?rev=379591&view=rev
Log:
Fix mod_asis docs re: use of HTTP/CGI headers.
Modified:
httpd/httpd/branches/2.0.x/docs/manual/mod/mod_asis.xml
httpd/httpd/branches/2.2.x/docs/manual/mod/mod_asis.xml
httpd/httpd/trunk/docs/manual/mod/mod_asis.xml
Modified: httpd/httpd/branches/2.0.x/docs/manual/mod/mod_asis.xml
URL: http://svn.apache.org/viewcvs/httpd/httpd/branches/2.0.x/docs/manual/mod/mod_asis.xml?rev=379591&r1=379590&r2=379591&view=diff
==============================================================================
--- httpd/httpd/branches/2.0.x/docs/manual/mod/mod_asis.xml (original)
+++ httpd/httpd/branches/2.0.x/docs/manual/mod/mod_asis.xml Tue Feb 21 13:19:37 2006
@@ -55,10 +55,11 @@
<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
Modified: httpd/httpd/branches/2.2.x/docs/manual/mod/mod_asis.xml
URL: http://svn.apache.org/viewcvs/httpd/httpd/branches/2.2.x/docs/manual/mod/mod_asis.xml?rev=379591&r1=379590&r2=379591&view=diff
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/mod/mod_asis.xml (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/mod/mod_asis.xml Tue Feb 21 13:19:37 2006
@@ -55,10 +55,10 @@
<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
Modified: httpd/httpd/trunk/docs/manual/mod/mod_asis.xml
URL: http://svn.apache.org/viewcvs/httpd/httpd/trunk/docs/manual/mod/mod_asis.xml?rev=379591&r1=379590&r2=379591&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_asis.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_asis.xml Tue Feb 21 13:19:37 2006
@@ -55,10 +55,10 @@
<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