From a6810d012600d9a67510a7a1d851e4504c6731f7 Mon Sep 17 00:00:00 2001
From: Rich Bowen <rbowen@apache.org>
Date: Wed, 19 May 2010 21:58:55 +0000
Subject: [PATCH] vhosts section of avoid doc.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@946433 13f79535-47bb-0310-9956-ffa450edef68
---
 docs/manual/rewrite/avoid.html.en | 18 +++++++++++++++++-
 docs/manual/rewrite/avoid.xml     | 18 +++++++++++++++++-
 2 files changed, 34 insertions(+), 2 deletions(-)

diff --git a/docs/manual/rewrite/avoid.html.en b/docs/manual/rewrite/avoid.html.en
index 7c473958b7..65709de040 100644
--- a/docs/manual/rewrite/avoid.html.en
+++ b/docs/manual/rewrite/avoid.html.en
@@ -134,7 +134,23 @@ server.</p>
 <div class="section">
 <h2><a name="vhosts" id="vhosts">Virtual Hosting</a></h2>
 <p>Although it is possible to handle <a href="vhosts.html">virtual hosts
-with mod_rewrite</a>, it is </p>
+with mod_rewrite</a>, it is seldom the right way. Creating individual
+&lt;VirtualHost&gt; blocks is almost always the right way to go. In the
+event that you have an enormous number of virtual hosts, consider using
+<code class="module"><a href="../mod/mod_vhost_alias.html">mod_vhost_alias</a></code> to crate these hosts automatically.</p>
+
+<p>Third-party modules sucha as <a href="link_needed">mod_macro</a> are
+also useful for creating a large number of virtual hosts dymaically.</p>
+
+<p>Using <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> for vitualhost creation may be
+appropriate if you are using a hosting service that does not provide
+you access to the server configuration files, and you are therefore
+restricted to configuration using <code>.htaccess</code> files.</p>
+
+<p>See the <a href="vhosts.html">virtual hosts with mod_rewrite</a>
+document for more details on how you might accomplish this if it still
+seems like the right approach.</p>
+
 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
 <div class="section">
 <h2><a name="proxy" id="proxy">Simple Proxying</a></h2>
diff --git a/docs/manual/rewrite/avoid.xml b/docs/manual/rewrite/avoid.xml
index fd9006e34a..41f7c7c405 100644
--- a/docs/manual/rewrite/avoid.xml
+++ b/docs/manual/rewrite/avoid.xml
@@ -144,7 +144,23 @@ server.</p>
 
 <section id="vhosts"><title>Virtual Hosting</title>
 <p>Although it is possible to handle <a href="vhosts.html">virtual hosts
-with mod_rewrite</a>, it is </p>
+with mod_rewrite</a>, it is seldom the right way. Creating individual
+&lt;VirtualHost&gt; blocks is almost always the right way to go. In the
+event that you have an enormous number of virtual hosts, consider using
+<module>mod_vhost_alias</module> to crate these hosts automatically.</p>
+
+<p>Third-party modules sucha as <a href="link_needed">mod_macro</a> are
+also useful for creating a large number of virtual hosts dymaically.</p>
+
+<p>Using <module>mod_rewrite</module> for vitualhost creation may be
+appropriate if you are using a hosting service that does not provide
+you access to the server configuration files, and you are therefore
+restricted to configuration using <code>.htaccess</code> files.</p>
+
+<p>See the <a href="vhosts.html">virtual hosts with mod_rewrite</a>
+document for more details on how you might accomplish this if it still
+seems like the right approach.</p>
+
 </section>
 
 <section id="proxy"><title>Simple Proxying</title>
-- 
2.50.1