From: Vincent Bray mod_rewrite
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.
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
@@ -387,7 +387,7 @@ RewriteRule ^(.+) http://webserverB.dom/$1 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 viamod_rewrite
? + be implemented viamod_rewrite
?
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 foo.html
- is rewritten to foo.NS.html
and and the
+ is rewritten to foo.NS.html
and the
rewriting stops. If the browser is "Lynx" or "Mozilla" of
version 1 or 2 the URL becomes foo.20.html
.
All other browsers receive page foo.32.html
.
@@ -637,7 +637,7 @@ www IN A 1.2.3.5
resolved, BIND
gives out www0-www5
- 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 www.foo.com
@@ -753,7 +753,7 @@ while (<STDIN>) {
let us configure a new file type with extension
.scgi
(for secure CGI) which will be processed
by the popular cgiwrap
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
/u/user/foo/bar.scgi
. But
cgiwrap
needs the URL in the form
@@ -767,11 +767,11 @@ RewriteRule ^/[uge]/([^/]+)/\.www/(.+)\.scgi(.*) ...
Or assume we have some more nifty programs:
wwwlog
(which displays the
- access.log
for a URL subtree and
+ access.log
for a URL subtree) and
wwwidx
(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 swwidx
program from within
/u/user/foo/
via hyperlink to