You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by sl...@apache.org on 2007/08/01 19:53:15 UTC
svn commit: r561889 - in /httpd/httpd/branches/2.2.x/docs/manual:
misc/rewriteguide.html.en misc/rewriteguide.xml
rewrite/rewrite_guide_advanced.html.en rewrite/rewrite_guide_advanced.xml
Author: slive
Date: Wed Aug 1 10:53:13 2007
New Revision: 561889
URL: http://svn.apache.org/viewvc?view=rev&rev=561889
Log:
Backport rewrite load balancing fix.
Modified:
httpd/httpd/branches/2.2.x/docs/manual/misc/rewriteguide.html.en
httpd/httpd/branches/2.2.x/docs/manual/misc/rewriteguide.xml
httpd/httpd/branches/2.2.x/docs/manual/rewrite/rewrite_guide_advanced.html.en
httpd/httpd/branches/2.2.x/docs/manual/rewrite/rewrite_guide_advanced.xml
Modified: httpd/httpd/branches/2.2.x/docs/manual/misc/rewriteguide.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/misc/rewriteguide.html.en?view=diff&rev=561889&r1=561888&r2=561889
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/misc/rewriteguide.html.en (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/misc/rewriteguide.html.en Wed Aug 1 10:53:13 2007
@@ -1262,19 +1262,15 @@
<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
Modified: httpd/httpd/branches/2.2.x/docs/manual/misc/rewriteguide.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/misc/rewriteguide.xml?view=diff&rev=561889&r1=561888&r2=561889
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/misc/rewriteguide.xml (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/misc/rewriteguide.xml Wed Aug 1 10:53:13 2007
@@ -1263,19 +1263,15 @@
<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
Modified: httpd/httpd/branches/2.2.x/docs/manual/rewrite/rewrite_guide_advanced.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/rewrite/rewrite_guide_advanced.html.en?view=diff&rev=561889&r1=561888&r2=561889
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/rewrite/rewrite_guide_advanced.html.en (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/rewrite/rewrite_guide_advanced.html.en Wed Aug 1 10:53:13 2007
@@ -619,19 +619,15 @@
<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
Modified: httpd/httpd/branches/2.2.x/docs/manual/rewrite/rewrite_guide_advanced.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/rewrite/rewrite_guide_advanced.xml?view=diff&rev=561889&r1=561888&r2=561889
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/rewrite/rewrite_guide_advanced.xml (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/rewrite/rewrite_guide_advanced.xml Wed Aug 1 10:53:13 2007
@@ -623,19 +623,15 @@
<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