You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by ji...@apache.org on 2009/03/24 16:15:00 UTC

svn commit: r757836 - /httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy.xml

Author: jim
Date: Tue Mar 24 15:14:56 2009
New Revision: 757836

URL: http://svn.apache.org/viewvc?rev=757836&view=rev
Log:
Docs are easier than code sometimes

Modified:
    httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy.xml

Modified: httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy.xml?rev=757836&r1=757835&r2=757836&view=diff
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy.xml (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy.xml Tue Mar 24 15:14:56 2009
@@ -805,7 +805,8 @@
     </table>
 
     <p>If the Proxy directive scheme starts with the
-    <code>balancer://</code> then a virtual worker that does not really
+    <code>balancer://</code> (eg: <code>balancer://cluster/</code>, 
+    any path information is ignored)  then a virtual worker that does not really
     communicate with the backend server will be created. Instead it is responsible
     for the management of several "real" workers. In that case the special set of
     parameters can be add to this virtual worker. See <module>mod_proxy_balancer</module>