<li><img alt="" src="../images/down.gif" /> <a href="#archive-access-multiplexer">Redirecting to Geographically Distributed Servers</a></li>
<li><img alt="" src="../images/down.gif" /> <a href="#browser-dependent-content">Browser Dependent Content</a></li>
<li><img alt="" src="../images/down.gif" /> <a href="#canonicalurl">Canonical URLs</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#uservhosts">Virtual Hosts Per User</a></li>
<li><img alt="" src="../images/down.gif" /> <a href="#moveddocroot">Moved <code>DocumentRoot</code></a></li>
<li><img alt="" src="../images/down.gif" /> <a href="#fallback-resource">Fallback Resource</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#mass-virtual-hosting">Mass Virtual Hosting</a></li>
</ul><h3>See also</h3><ul class="seealso"><li><a href="../mod/mod_rewrite.html">Module documentation</a></li><li><a href="intro.html">mod_rewrite introduction</a></li><li><a href="access.html">Controlling access</a></li><li><a href="vhosts.html">Virtual hosts</a></li><li><a href="proxy.html">Proxying</a></li><li><a href="advanced.html">Advanced techniques and tricks</a></li><li><a href="avoid.html">When not to use mod_rewrite</a></li></ul></div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
</dd>
</dl>
-</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="section">
-<h2><a name="uservhosts" id="uservhosts">Virtual Hosts Per User</a></h2>
-
-
-
- <dl>
- <dt>Description:</dt>
-
- <dd>
- <p>We want to automatically create a virtual host for every user who
- has an account on our web server system, without having to create
- new VirtualHost sections.</p>
-
- <p>In this recipe, we assume that we'll be using the hostname
- <code>www.<strong>username</strong>.example.com</code> for each
- user, and serve their content out of
- <code>/home/<strong>username</strong>/www</code>.</p>
- </dd>
-
- <dt>Solution:</dt>
-
- <dd>
-
-<div class="example"><pre>
-RewriteEngine on
-RewriteCond %{<strong>HTTP_HOST</strong>} ^www\.<strong>([^.]+)</strong>\.example\.com$
-RewriteRule ^(.*) /home/<strong>%1</strong>/www$1
-</pre></div></dd>
-
-<dt>Discussion</dt>
- <dd>
-
- <div class="warning">You will need to take care of the DNS
- resolution - Apache does
- not handle name resolution. You'll need either to create CNAME
- records for each hostname, or a DNS wildcard record. Creating DNS
- records is beyond the scope of this document.</div>
-
-<p>Parentheses used in a <code class="directive"><a href="../mod/mod_rewrite.html#rewritecond">RewriteCond</a></code> are captured into the
-backreferences <code>%1</code>, <code>%2</code>, etc, while parentheses
-used in <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> are
-captured into the backreferences <code>$1</code>, <code>$2</code>,
-etc.</p>
-
-<p>
-As with many techniques discussed in this document, mod_rewrite really
-isn't the best way to accomplish this task. You should, instead,
-consider using <code class="module"><a href="../mod/mod_vhost_alias.html">mod_vhost_alias</a></code> instead, as it will much
-more gracefully handle anything beyond serving static files, such as any
-dynamic content, and Alias resolution.
-</p>
- </dd>
- </dl>
-
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="moveddocroot" id="moveddocroot">Moved <code>DocumentRoot</code></a></h2>
</dl>
-</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
-<div class="section">
-<h2><a name="mass-virtual-hosting" id="mass-virtual-hosting">Mass Virtual Hosting</a></h2>
-
-
-
- <dl>
- <dt>Description:</dt>
-
- <dd>
- <p>Mass virtual hosting is one of the more common uses of
- mod_rewrite. However, it is seldom the best way to handle mass
- virtual hosting. This topic is discussed at great length in the <a href="../vhosts/mass.html">virtual host documentation</a>.</p>
- </dd>
- </dl>
-
</div></div>
<div class="bottomlang">
<p><span>Available Languages: </span><a href="../en/rewrite/remapping.html" title="English"> en </a></p>
</section>
-<section id="uservhosts">
-
- <title>Virtual Hosts Per User</title>
-
- <dl>
- <dt>Description:</dt>
-
- <dd>
- <p>We want to automatically create a virtual host for every user who
- has an account on our web server system, without having to create
- new VirtualHost sections.</p>
-
- <p>In this recipe, we assume that we'll be using the hostname
- <code>www.<strong>username</strong>.example.com</code> for each
- user, and serve their content out of
- <code>/home/<strong>username</strong>/www</code>.</p>
- </dd>
-
- <dt>Solution:</dt>
-
- <dd>
-
-<example><pre>
-RewriteEngine on
-RewriteCond %{<strong>HTTP_HOST</strong>} ^www\.<strong>([^.]+)</strong>\.example\.com$
-RewriteRule ^(.*) /home/<strong>%1</strong>/www$1
-</pre></example></dd>
-
-<dt>Discussion</dt>
- <dd>
-
- <note type="warning">You will need to take care of the DNS
- resolution - Apache does
- not handle name resolution. You'll need either to create CNAME
- records for each hostname, or a DNS wildcard record. Creating DNS
- records is beyond the scope of this document.</note>
-
-<p>Parentheses used in a <directive
-module="mod_rewrite">RewriteCond</directive> are captured into the
-backreferences <code>%1</code>, <code>%2</code>, etc, while parentheses
-used in <directive module="mod_rewrite">RewriteRule</directive> are
-captured into the backreferences <code>$1</code>, <code>$2</code>,
-etc.</p>
-
-<p>
-As with many techniques discussed in this document, mod_rewrite really
-isn't the best way to accomplish this task. You should, instead,
-consider using <module>mod_vhost_alias</module> instead, as it will much
-more gracefully handle anything beyond serving static files, such as any
-dynamic content, and Alias resolution.
-</p>
- </dd>
- </dl>
-
-</section>
-
<section id="moveddocroot">
<title>Moved <code>DocumentRoot</code></title>
</section>
-<section id="mass-virtual-hosting">
-
- <title>Mass Virtual Hosting</title>
-
- <dl>
- <dt>Description:</dt>
-
- <dd>
- <p>Mass virtual hosting is one of the more common uses of
- mod_rewrite. However, it is seldom the best way to handle mass
- virtual hosting. This topic is discussed at great length in the <a
- href="../vhosts/mass.html">virtual host documentation</a>.</p>
- </dd>
- </dl>
-
-</section>
-
</manualpage>
</div>
<div id="quickview"><h3>See also</h3><ul class="seealso"><li><a href="../mod/mod_rewrite.html">Module documentation</a></li><li><a href="intro.html">mod_rewrite introduction</a></li><li><a href="remapping.html">Redirection and remapping</a></li><li><a href="access.html">Controlling access</a></li><li><a href="proxy.html">Proxying</a></li><li><a href="advanced.html">Advanced techniques and tricks</a></li><li><a href="avoid.html">When not to use mod_rewrite</a></li></ul></div>
-</div>
+<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="uservhosts" id="uservhosts">Virtual Hosts Per User</a></h2>
+
+
+
+ <dl>
+ <dt>Description:</dt>
+
+ <dd>
+ <p>We want to automatically create a virtual host for every user who
+ has an account on our web server system, without having to create
+ new VirtualHost sections.</p>
+
+ <p>In this recipe, we assume that we'll be using the hostname
+ <code>www.<strong>username</strong>.example.com</code> for each
+ user, and serve their content out of
+ <code>/home/<strong>username</strong>/www</code>.</p>
+ </dd>
+
+ <dt>Solution:</dt>
+
+ <dd>
+
+<div class="example"><pre>
+RewriteEngine on
+RewriteCond %{<strong>HTTP_HOST</strong>} ^www\.<strong>([^.]+)</strong>\.example\.com$
+RewriteRule ^(.*) /home/<strong>%1</strong>/www$1
+</pre></div></dd>
+
+<dt>Discussion</dt>
+ <dd>
+
+ <div class="warning">You will need to take care of the DNS
+ resolution - Apache does
+ not handle name resolution. You'll need either to create CNAME
+ records for each hostname, or a DNS wildcard record. Creating DNS
+ records is beyond the scope of this document.</div>
+
+<p>Parentheses used in a <code class="directive"><a href="../mod/mod_rewrite.html#rewritecond">RewriteCond</a></code> are captured into the
+backreferences <code>%1</code>, <code>%2</code>, etc, while parentheses
+used in <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> are
+captured into the backreferences <code>$1</code>, <code>$2</code>,
+etc.</p>
+
+<p>
+As with many techniques discussed in this document, mod_rewrite really
+isn't the best way to accomplish this task. You should, instead,
+consider using <code class="module"><a href="../mod/mod_vhost_alias.html">mod_vhost_alias</a></code> instead, as it will much
+more gracefully handle anything beyond serving static files, such as any
+dynamic content, and Alias resolution.
+</p>
+ </dd>
+ </dl>
+
+</div></div>
<div class="bottomlang">
<p><span>Available Languages: </span><a href="../en/rewrite/vhosts.html" title="English"> en </a></p>
</div><div id="footer">
<seealso><a href="advanced.html">Advanced techniques and tricks</a></seealso>
<seealso><a href="avoid.html">When not to use mod_rewrite</a></seealso>
+<section id="uservhosts">
+
+ <title>Virtual Hosts Per User</title>
+
+ <dl>
+ <dt>Description:</dt>
+
+ <dd>
+ <p>We want to automatically create a virtual host for every user who
+ has an account on our web server system, without having to create
+ new VirtualHost sections.</p>
+
+ <p>In this recipe, we assume that we'll be using the hostname
+ <code>www.<strong>username</strong>.example.com</code> for each
+ user, and serve their content out of
+ <code>/home/<strong>username</strong>/www</code>.</p>
+ </dd>
+
+ <dt>Solution:</dt>
+
+ <dd>
+
+<example><pre>
+RewriteEngine on
+RewriteCond %{<strong>HTTP_HOST</strong>} ^www\.<strong>([^.]+)</strong>\.example\.com$
+RewriteRule ^(.*) /home/<strong>%1</strong>/www$1
+</pre></example></dd>
+
+<dt>Discussion</dt>
+ <dd>
+
+ <note type="warning">You will need to take care of the DNS
+ resolution - Apache does
+ not handle name resolution. You'll need either to create CNAME
+ records for each hostname, or a DNS wildcard record. Creating DNS
+ records is beyond the scope of this document.</note>
+
+<p>Parentheses used in a <directive
+module="mod_rewrite">RewriteCond</directive> are captured into the
+backreferences <code>%1</code>, <code>%2</code>, etc, while parentheses
+used in <directive module="mod_rewrite">RewriteRule</directive> are
+captured into the backreferences <code>$1</code>, <code>$2</code>,
+etc.</p>
+
+<p>
+As with many techniques discussed in this document, mod_rewrite really
+isn't the best way to accomplish this task. You should, instead,
+consider using <module>mod_vhost_alias</module> instead, as it will much
+more gracefully handle anything beyond serving static files, such as any
+dynamic content, and Alias resolution.
+</p>
+ </dd>
+ </dl>
+
+</section>
+
</manualpage>
projects / apache / commitdiff