[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-cvs
Subject:    svn commit: r949190 - in /httpd/httpd/trunk/docs/manual/rewrite:
From:       rbowen () apache ! org
Date:       2010-05-28 14:39:46
Message-ID: 20100528143946.A5DBC238897A () eris ! apache ! org
[Download RAW message or body]

Author: rbowen
Date: Fri May 28 14:39:46 2010
New Revision: 949190

URL: http://svn.apache.org/viewvc?rev=949190&view=rev
Log:
Several typos fixed.

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

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=949190&r1=949189&r2=949190&view=diff
 ==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/avoid.html.en (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/avoid.html.en Fri May 28 14:39:46 2010
@@ -112,7 +112,7 @@ task in a <code>.htaccess</code> file in
 <p>The <code class="directive"><a \
href="../mod/mod_alias.html#alias">Alias</a></code> directive  provides mapping from \
a URI to a directory - usually a directory outside  of your <code \
class="directive"><a href="../mod/core.html#documentroot">DocumentRoot</a></code>. \
                Although it
-is possible to perform this mappint with <code>mod_rewrite</code>,
+is possible to perform this mapping with <code>mod_rewrite</code>,
 <code>Alias</code> is the preferred method, for reasons of simplicity
 and performance.</p>
 
@@ -137,10 +137,10 @@ server.</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> +<code class="module"><a \
href="../mod/mod_vhost_alias.html">mod_vhost_alias</a></code> to create 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>Third-party modules such as <a href="link_needed">mod_macro</a> are
+also useful for creating a large number of virtual hosts dynamically.</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 @@ -154,7 \
+154,11 @@ 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>
-<p>ProxyPass</p>
+
+<p><code>RewriteRule</code> provides the <a href="flags.html#flag_p">[P]</a> flag to \
pass rewritten URIs through +<code class="module"><a \
href="../mod/mod_proxy.html">mod_proxy</a></code>. As with any use of \
<code>mod_rewrite</code>, +you want to ask yourself whether it's really the best \
solution.</p> +
 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" \
/></a></div>  <div class="section">
 <h2><a name="setenv" id="setenv">Environment Variable Testing</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=949190&r1=949189&r2=949190&view=diff
 ==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/avoid.xml (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/avoid.xml Fri May 28 14:39:46 2010
@@ -122,7 +122,7 @@ task in a <code>.htaccess</code> file in
 <p>The <directive module="mod_alias">Alias</directive> directive
 provides mapping from a URI to a directory - usually a directory outside
 of your <directive module="core">DocumentRoot</directive>. Although it
-is possible to perform this mappint with <code>mod_rewrite</code>,
+is possible to perform this mapping with <code>mod_rewrite</code>,
 <code>Alias</code> is the preferred method, for reasons of simplicity
 and performance.</p>
 
@@ -164,7 +164,12 @@ seems like the right approach.</p>
 </section>
 
 <section id="proxy"><title>Simple Proxying</title>
-<p>ProxyPass</p>
+
+<p><code>RewriteRule</code> provides the <a
+href="flags.html#flag_p">[P]</a> flag to pass rewritten URIs through
+<module>mod_proxy</module>. As with any use of <code>mod_rewrite</code>,
+you want to ask yourself whether it's really the best solution.</p>
+
 </section>
 
 <section id="setenv"><title>Environment Variable Testing</title>

Modified: httpd/httpd/trunk/docs/manual/rewrite/flags.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/rewrite/flags.html.en?rev=949190&r1=949189&r2=949190&view=diff
 ==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/flags.html.en (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/flags.html.en Fri May 28 14:39:46 2010
@@ -223,7 +223,7 @@ variables work.</p>
 contexts, including CGI programs, other RewriteRule directives, or
 CustomLog directives.</p>
 
-<p>The following example sets an evironment variable called 'image' to a
+<p>The following example sets an environment variable called 'image' to a
 value of '1' if the requested URI is an image file. Then, that
 environment variable is used to exclude those requests from the access
 log.</p>


[prev in list] [next in list] [prev in thread] [next in thread]