<p>The balancerurl is only needed when not in <code><Proxy <var>balancer://</var>...></code>
container directive. It corresponds to the url of a balancer defined in
<directive module="mod_proxy">ProxyPass</directive> directive.</p>
+ <p>The path component of the balancer URL in any
+ <code><Proxy <var>balancer://</var>...></code> container directive
+ is ignored.</p>
+ <p>Trailing slashes should typically be removed from the URL of a
+ <code>BalancerMember</code>.</p>
</usage>
</directivesynopsis>
<example>
<highlight language="config">
<Proxy balancer://hotcluster>
- BalancerMember http://www2.example.com:8080/ loadfactor=1
- BalancerMember http://www3.example.com:8080/ loadfactor=2
+ BalancerMember http://www2.example.com:8080 loadfactor=1
+ BalancerMember http://www3.example.com:8080 loadfactor=2
ProxySet lbmethod=bytraffic
</Proxy>
</highlight>
</table>
<p>If the Proxy directive scheme starts with the
- <code>balancer://</code> (eg: <code>balancer://cluster/</code>,
+ <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
ProxyPass /special-area http://special.example.com smax=5 max=10
ProxyPass / balancer://mycluster/ stickysession=JSESSIONID|jsessionid nofailover=On
<Proxy balancer://mycluster>
- BalancerMember ajp://1.2.3.4:8009/
- BalancerMember ajp://1.2.3.5:8009/ loadfactor=20
+ BalancerMember ajp://1.2.3.4:8009
+ BalancerMember ajp://1.2.3.5:8009 loadfactor=20
# Less powerful server, don't send as many requests there,
- BalancerMember ajp://1.2.3.6:8009/ loadfactor=5
+ BalancerMember ajp://1.2.3.6:8009 loadfactor=5
</Proxy>
</highlight>
<p>Setting up a hot-standby, that will only be used if no other
members are available</p>
<highlight language="config">
-ProxyPass / balancer://hotcluster/
+ProxyPass / balancer://hotcluster/
<Proxy balancer://hotcluster>
- BalancerMember ajp://1.2.3.4:8009/ loadfactor=1
- BalancerMember ajp://1.2.3.5:8009/ loadfactor=2
+ BalancerMember ajp://1.2.3.4:8009 loadfactor=1
+ BalancerMember ajp://1.2.3.5:8009 loadfactor=2
# The server below is on hot standby
- BalancerMember ajp://1.2.3.6:8009/ status=+H
+ BalancerMember ajp://1.2.3.6:8009 status=+H
ProxySet lbmethod=bytraffic
</Proxy>
</highlight>
</p>
<highlight language="config">
-<Proxy balancer://mycluster/>
- BalancerMember http://192.168.1.50:80/
- BalancerMember http://192.168.1.51:80/
+<Proxy balancer://mycluster>
+ BalancerMember http://192.168.1.50:80
+ BalancerMember http://192.168.1.51:80
</Proxy>
-ProxyPass /test balancer://mycluster/
-ProxyPassReverse /test balancer://mycluster/
+ProxyPass /test balancer://mycluster
+ProxyPassReverse /test balancer://mycluster
</highlight>
<p>Another example of how to provide load balancing with stickyness
<highlight language="config">
Header add Set-Cookie "ROUTEID=.%{BALANCER_WORKER_ROUTE}e; path=/" env=BALANCER_ROUTE_CHANGED
-<Proxy balancer://mycluster/>
- BalancerMember http://192.168.1.50:80/ route=1
- BalancerMember http://192.168.1.51:80/ route=2
+<Proxy balancer://mycluster>
+ BalancerMember http://192.168.1.50:80 route=1
+ BalancerMember http://192.168.1.51:80 route=2
ProxySet stickysession=ROUTEID
</Proxy>
-ProxyPass /test balancer://mycluster/
-ProxyPassReverse /test balancer://mycluster/
+ProxyPass /test balancer://mycluster
+ProxyPassReverse /test balancer://mycluster
</highlight>
</section>
<dt><var><a name="balancer_name" id="balancer_name">BALANCER_NAME</a></var></dt>
<dd>
<p>This is assigned the name of the balancer used for the current
- request. The value is something like <code>balancer://foo/</code>.</p>
+ request. The value is something like <code>balancer://foo</code>.</p>
</dd>
<!-- ============= BALANCER_WORKER_NAME ================== -->
configuring the name of the cookie and the name of the URL parameter
separated by a vertical bar (<code>|</code>) as in the following example:</p>
<highlight language="config">
-ProxyPass /test balancer://mycluster/ stickysession=JSESSIONID|jsessionid scolonpathdelim=On
+ProxyPass /test balancer://mycluster stickysession=JSESSIONID|jsessionid scolonpathdelim=On
<Proxy balancer://mycluster>
- BalancerMember http://192.168.1.50:80/ route=node1
- BalancerMember http://192.168.1.51:80/ route=node2
+ BalancerMember http://192.168.1.50:80 route=node1
+ BalancerMember http://192.168.1.51:80 route=node2
</Proxy>
</highlight>
<p>If the cookie and the request parameter both provide routing information
<highlight language="config">
ProxyPass /myapp/ balancer://myappcluster/
<Proxy balancer://myappcluster/>
- BalancerMember fcgi://localhost:4000/
- BalancerMember fcgi://localhost:4001/
+ BalancerMember fcgi://localhost:4000
+ BalancerMember fcgi://localhost:4001
</Proxy>
</highlight>
</example>
<example><title>Balanced gateway</title>
<highlight language="config">
ProxyPass /scgi-bin/ balancer://somecluster/
-<Proxy balancer://somecluster/>
- BalancerMember scgi://localhost:4000/
- BalancerMember scgi://localhost:4001/
+<Proxy balancer://somecluster>
+ BalancerMember scgi://localhost:4000
+ BalancerMember scgi://localhost:4001
</Proxy>
</highlight>
</example>
projects / apache / commitdiff