Mailing-List: contact cvs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Date: 3 Aug 2004 21:33:17 -0000
Message-ID: <20040803213317.8207.qmail@minotaur.apache.org>
From: rbowen@apache.org
To: httpd-docs-1.3-cvs@apache.org
Subject: cvs commit: httpd-docs-1.3/htdocs/manual/misc rewriteguide.html

rbowen      2004/08/03 14:33:17

  Modified:    htdocs/manual/misc rewriteguide.html
  Log:
  A few gramatical tweaks, and the introduction of some actual text
  instead of a "..." which has been there For All Time.
  
  Revision  Changes    Path
  1.20      +12 -4     httpd-docs-1.3/htdocs/manual/misc/rewriteguide.html
  
  Index: rewriteguide.html
  ===================================================================
  RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/misc/rewriteguide.html,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- rewriteguide.html	7 Jul 2003 21:32:12 -0000	1.19
  +++ rewriteguide.html	3 Aug 2004 21:33:17 -0000	1.20
  @@ -29,15 +29,15 @@
         <p>This document supplements the mod_rewrite <a
         href="../mod/mod_rewrite.html">reference documentation</a>.
         It describes how one can use Apache's mod_rewrite to solve
  -      typical URL-based problems webmasters are usually confronted
  -      with in practice. I give detailed descriptions on how to
  +      typical URL-based problems with which webmasters are often 
  +      confronted. We give detailed descriptions on how to
         solve each problem by configuring URL rewriting rulesets.</p>
   
         <h2><a id="ToC1" name="ToC1">Introduction to
         mod_rewrite</a></h2>
         The Apache module mod_rewrite is a killer one, i.e. it is a
         really sophisticated module which provides a powerful way to
  -      do URL manipulations. With it you can nearly do all types of
  +      do URL manipulations. With it you can do nearly all types of
         URL manipulations you ever dreamed about. The price you have
         to pay is to accept complexity, because mod_rewrite's major
         drawback is that it is not easy to understand and use for the
  @@ -114,7 +114,12 @@
         <dl>
           <dt><strong>Description:</strong></dt>
   
  -        <dd>...</dd>
  +        <dd>The goal of this rule is to force the use of a particular
  +        hostname, in preference to other hostnames which may be used to
  +        reach the same site. For example, if you wish to force the use
  +        of <strong>www.example.com</strong> instead of
  +        <strong>example.com</strong>, you might use a variant of the
  +        following recipe.</dd>
   
           <dt><strong>Solution:</strong></dt>
   
  @@ -124,10 +129,13 @@
               <tr>
                 <td>
   <pre>
  +# For sites running on a port other than 80
   RewriteCond %{HTTP_HOST}   !^fully\.qualified\.domain\.name [NC]
   RewriteCond %{HTTP_HOST}   !^$
   RewriteCond %{SERVER_PORT} !^80$
   RewriteRule ^/(.*)         http://fully.qualified.domain.name:%{SERVER_PORT}/$1 [L,R]
  +
  +# And for a site running on port 80
   RewriteCond %{HTTP_HOST}   !^fully\.qualified\.domain\.name [NC]
   RewriteCond %{HTTP_HOST}   !^$
   RewriteRule ^/(.*)         http://fully.qualified.domain.name/$1 [L,R]