From: Jeff Trawick Date: Wed, 23 Apr 2014 14:03:30 +0000 (+0000) Subject: tweaks to grammar and markup X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=5d9bf909dd1136b8e88c69b3dc5251246f3c1101;p=thirdparty%2Fapache%2Fhttpd.git tweaks to grammar and markup git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1589413 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_proxy_scgi.xml b/docs/manual/mod/mod_proxy_scgi.xml index 91942faa5bb..8b903a8a5ac 100644 --- a/docs/manual/mod/mod_proxy_scgi.xml +++ b/docs/manual/mod/mod_proxy_scgi.xml @@ -1,4 +1,4 @@ - + @@ -103,10 +103,10 @@ header

The ProxySCGISendfile directive enables the - SCGI backend to let files serve directly by the gateway. This is useful - performance purposes -- the httpd can use sendfile or other + SCGI backend to let files be served directly by the gateway. This is useful + for performance purposes — httpd can use sendfile or other optimizations, which are not possible if the file comes over the backend - socket.

+ socket. Additionally, the file contents are not transmitted twice.

The ProxySCGISendfile argument determines the gateway behaviour:

@@ -115,22 +115,22 @@ header
On
The gateway looks for a backend response header called - X-Sendfile and interprets the value as filename to serve. The - header is removed from the final response headers. This is equivalent to + X-Sendfile and interprets the value as the filename to serve. + The header is removed from the final response headers. This is equivalent to ProxySCGISendfile X-Sendfile.
anything else
Similar to On, but instead of the hardcoded header name - the argument is applied as header name.
+ X-Sendfile, the argument is used as the header name.
Example - # Use the default header (X-Sendfile) - ProxySCGISendfile On +# Use the default header (X-Sendfile) +ProxySCGISendfile On - # Use a different header - ProxySCGISendfile X-Send-Static +# Use a different header +ProxySCGISendfile X-Send-Static
@@ -148,11 +148,11 @@ backend

The ProxySCGIInternalRedirect enables the backend to internally redirect the gateway to a different URL. This feature - origins in mod_cgi, which internally redirects the - response, if the response status is OK (200) and + originates in mod_cgi, which internally redirects the + response if the response status is OK (200) and the response contains a Location header and its value starts with a slash (/). This value is interpreted as a new local - URL the apache internally redirects to.

+ URL that Apache httpd internally redirects to.

mod_proxy_scgi does the same as mod_cgi in this regard, except that you can turn off the