From: Jim Jagielski
Date: Thu, 13 Sep 2012 17:14:28 +0000 (+0000)
Subject: Best practice
X-Git-Tag: 2.5.0-alpha~6340
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=9b6e8036fb7c5872ed4bce5b14e1f2335fd5ad71;p=thirdparty%2Fapache%2Fhttpd.git
Best practice
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1384408 13f79535-47bb-0310-9956-ffa450edef68
---
diff --git a/docs/manual/mod/mod_proxy.xml b/docs/manual/mod/mod_proxy.xml
index 8f3da2d7b79..0691560c5ea 100644
--- a/docs/manual/mod/mod_proxy.xml
+++ b/docs/manual/mod/mod_proxy.xml
@@ -696,8 +696,8 @@ expressions
<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>
@@ -1111,10 +1111,10 @@ ProxyPass /mirror/foo http://backend.example.com
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>
@@ -1123,10 +1123,10 @@ ProxyPass / balancer://mycluster/ stickysession=JSESSIONID|jsessionid nofailover
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>
diff --git a/docs/manual/mod/mod_proxy_balancer.xml b/docs/manual/mod/mod_proxy_balancer.xml
index 692a110bcba..94968ebaffa 100644
--- a/docs/manual/mod/mod_proxy_balancer.xml
+++ b/docs/manual/mod/mod_proxy_balancer.xml
@@ -92,12 +92,12 @@
-<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/
Another example of how to provide load balancing with stickyness
@@ -107,13 +107,13 @@ ProxyPassReverse /test balancer://mycluster
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/
@@ -140,7 +140,7 @@ ProxyPassReverse /test balancer://mycluster
BALANCER_NAME
This is assigned the name of the balancer used for the current
- request. The value is something like balancer://foo
.
+ request. The value is something like balancer://foo/
.
@@ -249,10 +249,10 @@ ProxyPassReverse /test balancer://mycluster
configuring the name of the cookie and the name of the URL parameter
separated by a vertical bar (|
) as in the following example:
-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>
If the cookie and the request parameter both provide routing information