Backport rewrite load balancing fix.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@561889 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/misc/rewriteguide.html.en b/docs/manual/misc/rewriteguide.html.en
index 845a224ee00626365071c8982adaf806f4366081..4ad31b1795d4e6fbc78ddef971c9705e26568d47 100644 (file)
--- a/docs/manual/misc/rewriteguide.html.en
+++ b/docs/manual/misc/rewriteguide.html.en
@@ -1262,19 +1262,15 @@ www5   IN  A       1.2.3.6
               <p>Then you additionally add the following entry:</p>
 
 <div class="example"><pre>
-www    IN  CNAME   www0.foo.com.
-       IN  CNAME   www1.foo.com.
-       IN  CNAME   www2.foo.com.
-       IN  CNAME   www3.foo.com.
-       IN  CNAME   www4.foo.com.
-       IN  CNAME   www5.foo.com.
-       IN  CNAME   www6.foo.com.
-</pre></div>
-
-              <p>Notice that this seems wrong, but is actually an
-              intended feature of <code>BIND</code> and can be used
-              in this way. However, now when <code>www.foo.com</code> gets
-              resolved, <code>BIND</code> gives out <code>www0-www6</code>
+www   IN  A       1.2.3.1
+www   IN  A       1.2.3.2
+www   IN  A       1.2.3.3
+www   IN  A       1.2.3.4
+www   IN  A       1.2.3.5
+</pre></div>
+
+              <p>Now when <code>www.foo.com</code> gets
+              resolved, <code>BIND</code> gives out <code>www0-www5</code>
               - but in a slightly permutated/rotated order every time.
               This way the clients are spread over the various
               servers. But notice that this not a perfect load

diff --git a/docs/manual/misc/rewriteguide.xml b/docs/manual/misc/rewriteguide.xml
index e9f5436e069ee219aa7bccb4f94576f602507db0..8a0d22cc71732ef3146324868d42846a94702d1e 100644 (file)
--- a/docs/manual/misc/rewriteguide.xml
+++ b/docs/manual/misc/rewriteguide.xml
@@ -1263,19 +1263,15 @@ www5   IN  A       1.2.3.6
               <p>Then you additionally add the following entry:</p>
 
 <example><pre>
-www    IN  CNAME   www0.foo.com.
-       IN  CNAME   www1.foo.com.
-       IN  CNAME   www2.foo.com.
-       IN  CNAME   www3.foo.com.
-       IN  CNAME   www4.foo.com.
-       IN  CNAME   www5.foo.com.
-       IN  CNAME   www6.foo.com.
-</pre></example>
-
-              <p>Notice that this seems wrong, but is actually an
-              intended feature of <code>BIND</code> and can be used
-              in this way. However, now when <code>www.foo.com</code> gets
-              resolved, <code>BIND</code> gives out <code>www0-www6</code>
+www   IN  A       1.2.3.1
+www   IN  A       1.2.3.2
+www   IN  A       1.2.3.3
+www   IN  A       1.2.3.4
+www   IN  A       1.2.3.5
+</pre></example>
+
+              <p>Now when <code>www.foo.com</code> gets
+              resolved, <code>BIND</code> gives out <code>www0-www5</code>
               - but in a slightly permutated/rotated order every time.
               This way the clients are spread over the various
               servers. But notice that this not a perfect load

diff --git a/docs/manual/rewrite/rewrite_guide_advanced.html.en b/docs/manual/rewrite/rewrite_guide_advanced.html.en
index b020eaa264a28c5b81f074abdaf9b34b3da80499..4d7d732d19e4345fda94a46e804889d3c2f4c1de 100644 (file)
--- a/docs/manual/rewrite/rewrite_guide_advanced.html.en
+++ b/docs/manual/rewrite/rewrite_guide_advanced.html.en
@@ -619,19 +619,15 @@ www5   IN  A       1.2.3.6
               <p>Then you additionally add the following entry:</p>
 
 <div class="example"><pre>
-www    IN  CNAME   www0.foo.com.
-       IN  CNAME   www1.foo.com.
-       IN  CNAME   www2.foo.com.
-       IN  CNAME   www3.foo.com.
-       IN  CNAME   www4.foo.com.
-       IN  CNAME   www5.foo.com.
-       IN  CNAME   www6.foo.com.
+www   IN  A       1.2.3.1
+www   IN  A       1.2.3.2
+www   IN  A       1.2.3.3
+www   IN  A       1.2.3.4
+www   IN  A       1.2.3.5
 </pre></div>
 
-              <p>Notice that this seems wrong, but is actually an
-              intended feature of <code>BIND</code> and can be used
-              in this way. However, now when <code>www.foo.com</code> gets
-              resolved, <code>BIND</code> gives out <code>www0-www6</code>
+              <p>Now when <code>www.foo.com</code> gets
+              resolved, <code>BIND</code> gives out <code>www0-www5</code>
               - but in a slightly permutated/rotated order every time.
               This way the clients are spread over the various
               servers. But notice that this not a perfect load

diff --git a/docs/manual/rewrite/rewrite_guide_advanced.xml b/docs/manual/rewrite/rewrite_guide_advanced.xml
index 9c9ed5f6c2d58b00df3e9a1ed27ab20d67cd648d..d264675cfec0d3c258b440cb1806542c1ed0a8ff 100644 (file)
--- a/docs/manual/rewrite/rewrite_guide_advanced.xml
+++ b/docs/manual/rewrite/rewrite_guide_advanced.xml
@@ -623,19 +623,15 @@ www5   IN  A       1.2.3.6
               <p>Then you additionally add the following entry:</p>
 
 <example><pre>
-www    IN  CNAME   www0.foo.com.
-       IN  CNAME   www1.foo.com.
-       IN  CNAME   www2.foo.com.
-       IN  CNAME   www3.foo.com.
-       IN  CNAME   www4.foo.com.
-       IN  CNAME   www5.foo.com.
-       IN  CNAME   www6.foo.com.
+www   IN  A       1.2.3.1
+www   IN  A       1.2.3.2
+www   IN  A       1.2.3.3
+www   IN  A       1.2.3.4
+www   IN  A       1.2.3.5
 </pre></example>
 
-              <p>Notice that this seems wrong, but is actually an
-              intended feature of <code>BIND</code> and can be used
-              in this way. However, now when <code>www.foo.com</code> gets
-              resolved, <code>BIND</code> gives out <code>www0-www6</code>
+              <p>Now when <code>www.foo.com</code> gets
+              resolved, <code>BIND</code> gives out <code>www0-www5</code>
               - but in a slightly permutated/rotated order every time.
               This way the clients are spread over the various
               servers. But notice that this not a perfect load