Commit 4b784d9f authored by Richard Bowen's avatar Richard Bowen
Browse files

As per bug # 22061, this paragraph was written prior to the

RedirectMatch directive, and thus was somewhat inaccurate. That, and it
contained just a few too many "trivial"s for my liking.



git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x@123578 13f79535-47bb-0310-9956-ffa450edef68
parent 4f969c6b
Loading
Loading
Loading
Loading
+10 −9
Changes for docs/manual/misc/rewriteguide.xml: 10 added lines, 9 removed lines.
Original line number Diff line number Diff line
@@ -180,20 +180,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>