You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by no...@apache.org on 2008/04/15 20:40:21 UTC
svn commit: r648370 -
/httpd/httpd/trunk/docs/manual/rewrite/rewrite_guide_advanced.html.en
Author: noodl
Date: Tue Apr 15 11:40:15 2008
New Revision: 648370
URL: http://svn.apache.org/viewvc?rev=648370&view=rev
Log:
Update transformations
Modified:
httpd/httpd/trunk/docs/manual/rewrite/rewrite_guide_advanced.html.en
Modified: httpd/httpd/trunk/docs/manual/rewrite/rewrite_guide_advanced.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/rewrite/rewrite_guide_advanced.html.en?rev=648370&r1=648369&r2=648370&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/rewrite_guide_advanced.html.en (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/rewrite_guide_advanced.html.en Tue Apr 15 11:40:15 2008
@@ -26,7 +26,7 @@
<a href="../mod/mod_rewrite.html">reference documentation</a>.
It describes how one can use Apache's <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>
to solve typical URL-based problems with which webmasters are
- commonony confronted. We give detailed descriptions on how to
+ commonly confronted. We give detailed descriptions on how to
solve each problem by configuring URL rewriting rulesets.</p>
<div class="warning">ATTENTION: Depending on your server configuration
@@ -45,7 +45,7 @@
<li><img alt="" src="../images/down.gif" /> <a href="#filereorg">Filesystem Reorganization</a></li>
<li><img alt="" src="../images/down.gif" /> <a href="#redirect404">Redirect Failing URLs To Other Webserver</a></li>
<li><img alt="" src="../images/down.gif" /> <a href="#archive-access-multiplexer">Archive Access Multiplexer</a></li>
-<li><img alt="" src="../images/down.gif" /> <a href="#browser-depedent-content">Browser Dependent Content</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="#dynamic-mirror">Dynamic Mirror</a></li>
<li><img alt="" src="../images/down.gif" /> <a href="#reverse-dynamic-mirror">Reverse Dynamic Mirror</a></li>
<li><img alt="" src="../images/down.gif" /> <a href="#retrieve-missing-data">Retrieve Missing Data from Intranet</a></li>
@@ -88,7 +88,7 @@
<dd>
<p>First, the knowledge of the target servers come from
(distributed) external maps which contain information
- where our users, groups and entities stay. The have the
+ where our users, groups and entities stay. They have the
form</p>
<div class="example"><pre>
@@ -387,7 +387,7 @@
near the location of the requesting client. Actually this
can be called an FTP access multiplexing service. While
CPAN runs via CGI scripts, how can a similar approach
- implemented via <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>?</p>
+ be implemented via <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>?</p>
</dd>
<dt>Solution:</dt>
@@ -425,7 +425,7 @@
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
-<h2><a name="browser-depedent-content" id="browser-depedent-content">Browser Dependent Content</a></h2>
+<h2><a name="browser-dependent-content" id="browser-dependent-content">Browser Dependent Content</a></h2>
@@ -445,10 +445,10 @@
<dd>
<p>We cannot use content negotiation because the browsers do
not provide their type in that form. Instead we have to
- act on the HTTP header "User-Agent". The following condig
+ act on the HTTP header "User-Agent". The following config
does the following: If the HTTP header "User-Agent"
begins with "Mozilla/3", the page <code>foo.html</code>
- is rewritten to <code>foo.NS.html</code> and and the
+ is rewritten to <code>foo.NS.html</code> and the
rewriting stops. If the browser is "Lynx" or "Mozilla" of
version 1 or 2 the URL becomes <code>foo.20.html</code>.
All other browsers receive page <code>foo.32.html</code>.
@@ -637,7 +637,7 @@
resolved, <code>BIND</code> gives out <code>www0-www5</code>
- but in a slightly permutated/rotated order every time.
This way the clients are spread over the various
- servers. But notice that this not a perfect load
+ servers. But notice that this is not a perfect load
balancing scheme, because DNS resolve information
gets cached by the other nameservers on the net, so
once a client has resolved <code>www.foo.com</code>
@@ -753,7 +753,7 @@
let us configure a new file type with extension
<code>.scgi</code> (for secure CGI) which will be processed
by the popular <code>cgiwrap</code> program. The problem
- here is that for instance we use a Homogeneous URL Layout
+ here is that for instance if we use a Homogeneous URL Layout
(see above) a file inside the user homedirs has the URL
<code>/u/user/foo/bar.scgi</code>. But
<code>cgiwrap</code> needs the URL in the form
@@ -767,11 +767,11 @@
<p>Or assume we have some more nifty programs:
<code>wwwlog</code> (which displays the
- <code>access.log</code> for a URL subtree and
+ <code>access.log</code> for a URL subtree) and
<code>wwwidx</code> (which runs Glimpse on a URL
subtree). We have to provide the URL area to these
programs so they know on which area they have to act on.
- But usually this ugly, because they are all the times
+ But usually this is ugly, because they are all the times
still requested from that areas, i.e. typically we would
run the <code>swwidx</code> program from within
<code>/u/user/foo/</code> via hyperlink to</p>
@@ -1092,7 +1092,7 @@
RewriteCond ${vhost:%1} ^(/.*)$
#
# 5. finally we can map the URL to its docroot location
-# and remember the virtual host for logging puposes
+# and remember the virtual host for logging purposes
RewriteRule ^/(.*)$ %1/$1 [E=VHOST:${lowercase:%{HTTP_HOST}}]
:
</pre></div>