PATH_INFO is set for free when we use SetHandler style configuration,

because we have already directory walked.

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

diff --git a/docs/manual/mod/mod_proxy_fcgi.xml b/docs/manual/mod/mod_proxy_fcgi.xml
index a92989ef2453ab192424b08c5a211d3dad3943dc..0b5e38d77599a87f587d083465a2da257f2db536 100644 (file)
--- a/docs/manual/mod/mod_proxy_fcgi.xml
+++ b/docs/manual/mod/mod_proxy_fcgi.xml
@@ -161,8 +161,10 @@ ProxyPass /myapp/ balancer://myappcluster/
     provider:</p>
     <dl>
         <dt>proxy-fcgi-pathinfo</dt>
-        <dd>By default <module>mod_proxy_fcgi</module> will neither create
-        nor export the <var>PATH_INFO</var> environment variable. This allows
+        <dd>When configured via <directive module="mod_proxy"
+        >ProxyPass</directive> or  <directive module="mod_proxy"
+        >ProxyPassMatch</directive>, <module>mod_proxy_fcgi</module> will not
+        set the <var>PATH_INFO</var> environment variable. This allows
         the backend FCGI server to correctly determine <var>SCRIPT_NAME</var>
         and <var>Script-URI</var> and be compliant with RFC 3875 section 3.3.
         If instead you need <module>mod_proxy_fcgi</module> to generate