Update the copyright year in all .c, .h and .xml files

[apache] / docs / manual / misc / rewriteguide.xml

diff --git a/docs/manual/misc/rewriteguide.xml b/docs/manual/misc/rewriteguide.xml
index 49a2963a6e879900aac2cfa00b07c81fd87e1a30..79da880e34f1446f509a557902cf9a3693e4436c 100644 (file)
--- a/docs/manual/misc/rewriteguide.xml
+++ b/docs/manual/misc/rewriteguide.xml
@@ -1,10 +1,11 @@
 <?xml version="1.0" encoding="UTF-8" ?>
 <!DOCTYPE manualpage SYSTEM "../style/manualpage.dtd">
 <?xml-stylesheet type="text/xsl" href="../style/manual.en.xsl"?>
-<!-- $Revision: 1.12 $ -->
+<!-- $LastChangedRevision$ -->
 
 <!--
- Copyright 2002-2004 The Apache Software Foundation
+ Copyright 2002-2006 The Apache Software Foundation or its licensors, as
+ applicable.
 
  Licensed under the Apache License, Version 2.0 (the "License");
  you may not use this file except in compliance with the License.
@@ -34,8 +35,8 @@
     <p>This document supplements the <module>mod_rewrite</module>
     <a href="../mod/mod_rewrite.html">reference documentation</a>.
     It describes how one can use Apache's <module>mod_rewrite</module>
-    to solve typical URL-based problems webmasters are usually confronted
-    with in practice. I give detailed descriptions on how to
+    to solve typical URL-based problems with which webmasters are
+    commonly confronted. We give detailed descriptions on how to
     solve each problem by configuring URL rewriting rulesets.</p>
 
   </summary>
@@ -46,8 +47,8 @@
 
     <p>The Apache module <module>mod_rewrite</module> 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 URL manipulations you ever dreamed about.
+    a powerful way to 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
     <module>mod_rewrite</module>'s major drawback is that it is
     not easy to understand and use for the beginner. And even
@@ -68,7 +69,7 @@
     <title>Practical Solutions</title>
 
     <p>Here come a lot of practical solutions I've either invented
-    myself or collected from other peoples solutions in the past.
+    myself or collected from other people's solutions in the past.
     Feel free to learn the black magic of URL rewriting from
     these examples.</p>
 
@@ -172,20 +173,21 @@ RewriteRule ^/(.*)         http://fully.qualified.domain.name/$1 [L,R]
         <dt>Solution:</dt>
 
         <dd>
-          <p>We just redirect the URL <code>/</code> to
-          <code>/e/www/</code>. While is seems trivial it is
-          actually trivial with <module>mod_rewrite</module>, only.
-          Because the typical old mechanisms of URL <em>Aliases</em>
-          (as provides by <module>mod_alias</module> and friends)
-          only used <em>prefix</em> matching. With this you cannot
-          do such a redirection because the <directive module="core"
-          >DocumentRoot</directive> is a prefix of all URLs. With
-          <module>mod_rewrite</module> it is really trivial:</p>
-
+          <p>We redirect the URL <code>/</code> to
+          <code>/e/www/</code>:
+          </p>
+         
 <example><pre>
 RewriteEngine on
 RewriteRule   <strong>^/$</strong>  /e/www/  [<strong>R</strong>]
 </pre></example>
+
+    <p>Note that this can also be handled using the <directive
+    module="mod_alias">RedirectMatch</directive> directive:</p>
+
+    <example>
+    RedirectMatch ^/$ http://example.com/e/www/
+    </example>
         </dd>
       </dl>
 
@@ -541,7 +543,7 @@ RewriteRule   (.*)                     netsw-lsdir.cgi/$1
 
     <section>
 
-      <title>NCSA imagemap to Apache <code>mod_imap</code></title>
+      <title>NCSA imagemap to Apache <code>mod_imagemap</code></title>
 
       <dl>
         <dt>Description:</dt>
@@ -551,7 +553,7 @@ RewriteRule   (.*)                     netsw-lsdir.cgi/$1
           modern Apache webserver a lot of people want a smooth
           transition. So they want pages which use their old NCSA
           <code>imagemap</code> program to work under Apache with the
-          modern <module>mod_imap</module>. The problem is that there
+          modern <module>mod_imagemap</module>. The problem is that there
           are a lot of hyperlinks around which reference the
           <code>imagemap</code> program via
           <code>/cgi-bin/imagemap/path/to/page.map</code>. Under