httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rbo...@apache.org
Subject svn commit: r946433 - in /httpd/httpd/trunk/docs/manual/rewrite: avoid.html.en avoid.xml
Date Wed, 19 May 2010 21:58:55 GMT
Author: rbowen
Date: Wed May 19 21:58:55 2010
New Revision: 946433

URL: http://svn.apache.org/viewvc?rev=946433&view=rev
Log:
vhosts section of avoid doc.

Modified:
    httpd/httpd/trunk/docs/manual/rewrite/avoid.html.en
    httpd/httpd/trunk/docs/manual/rewrite/avoid.xml

Modified: httpd/httpd/trunk/docs/manual/rewrite/avoid.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/rewrite/avoid.html.en?rev=946433&r1=946432&r2=946433&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/avoid.html.en (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/avoid.html.en Wed May 19 21:58:55 2010
@@ -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>

Modified: httpd/httpd/trunk/docs/manual/rewrite/avoid.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/rewrite/avoid.xml?rev=946433&r1=946432&r2=946433&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/avoid.xml (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/avoid.xml Wed May 19 21:58:55 2010
@@ -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>



Mime
View raw message