From 42753eb9edb702952d3bbb0cb7cb41e0c0a42567 Mon Sep 17 00:00:00 2001 From: Rich Bowen Date: Fri, 17 May 2002 17:06:27 +0000 Subject: [PATCH] Spelling corrections. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@95153 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/misc/rewriteguide.html | 44 +++++++++++++++--------------- 1 file changed, 22 insertions(+), 22 deletions(-) diff --git a/docs/manual/misc/rewriteguide.html b/docs/manual/misc/rewriteguide.html index edfe49c334..7ad778f62a 100644 --- a/docs/manual/misc/rewriteguide.html +++ b/docs/manual/misc/rewriteguide.html @@ -81,7 +81,7 @@
On some webservers there are more than one URL for a resource. Usually there are canonical URLs (which should be actually used and distributed) and those which are just - shortcuts, internal ones, etc. Independed which URL the + shortcuts, internal ones, etc. Independent of which URL the user supplied with the request he should finally see the canonical one only.
@@ -191,7 +191,7 @@ RewriteRule ^/$ /e/www/ [R] /~quux/foo instead of /~quux/foo/ then the server searches for a file named foo. And because this file is a directory it - complains. Actually is tries to fix it themself in most of + complains. Actually it tries to fix it itself in most of the cases, but sometimes this mechanism need to be emulated by you. For instance after you have done a lot of complicated URL rewritings to CGI scripts etc. @@ -253,12 +253,12 @@ RewriteRule ^(.+[^/])$ $1/ [R]
Description:
-
We want to create a homogenous and consistent URL +
We want to create a homogeneous and consistent URL layout over all WWW servers on a Intranet webcluster, i.e. all URLs (per definition server local and thus server - dependent!) become actually server independed! + dependent!) become actually server independent! What we want is to give the WWW namespace a consistent - server-independend layout: no URL should have to include + server-independent layout: no URL should have to include any physically correct target server. The cluster itself should drive us automatically to the physical target host.
@@ -326,7 +326,7 @@ RewriteRule ^/([uge])/([^/]+)/([^.]+.+) /$1/$2/.www/$3\
Description:
-
A lot of webmaster aksed for a solution to the +
Many webmasters have asked for a solution to the following situation: They wanted to redirect just all homedirs on a webserver to another webserver. They usually need such things when establishing a newer webserver which @@ -359,7 +359,7 @@ RewriteRule ^/~(.+) http://newserver/~$1 [R,L]
Description:
-
Some sites with thousend of users usually use a +
Some sites with thousands of users usually use a structured homedir layout, i.e. each homedir is in a subdirectory which begins for instance with the first character of the username. So, /~foo/anypath @@ -387,7 +387,7 @@ RewriteRule ^/~(([a-z])[a-z0-9]+)(.*) /home/$2
-

Filesystem Reorganisation

+

Filesystem Reorganization

Description:
@@ -583,7 +583,7 @@ RewriteRule ^/cgi-bin/imagemap(.*) $1 [PT]
Description:
-
Sometimes it is neccessary to let the webserver search +
Sometimes it is necessary to let the webserver search for pages in more than one directory. Here MultiViews or other techniques cannot help.
@@ -730,14 +730,14 @@ RewriteRule ^(/~.+) http://www.somewhere.com/$1 [R,L] failing requests on webserver A to webserver B. Usually this is done via ErrorDocument CGI-scripts in Perl, but there is also a mod_rewrite solution. But notice that this - is less performant than using a ErrorDocument + performs more poorly than using an ErrorDocument CGI-script!
Solution:
The first solution has the best performance but less - flexibility and is less error safe: + flexibility, and is less error safe: @@ -940,12 +940,12 @@ com ftp://ftp.cxan.com/CxAN/ -

Time-Dependend Rewriting

+

Time-Dependent Rewriting

Description:
-
When tricks like time-dependend content should happen a +
When tricks like time-dependent content should happen a lot of webmasters still use CGI scripts which do for instance redirects to specialized pages. How can it be done via mod_rewrite?
@@ -956,7 +956,7 @@ com ftp://ftp.cxan.com/CxAN/ There are a lot of variables named TIME_xxx for rewrite conditions. In conjunction with the special lexicographic comparison patterns <STRING, >STRING - and =STRING we can do time-dependend redirects: + and =STRING we can do time-dependent redirects:
@@ -1092,13 +1092,13 @@ RewriteRule ^foo\.html$ bar.html [ -

Browser Dependend Content

+

Browser Dependent Content

Description:
At least for important top-level pages it is sometimes - necesarry to provide the optimum of browser dependend + necessary to provide the optimum of browser dependent content, i.e. one has to provide a maximum version for the latest Netscape variants, a minimum version for the Lynx browsers and a average feature version for all others.
@@ -1220,7 +1220,7 @@ RewriteRule ^http://www\.remotesite\.com/(.*)$ /mirror/of/remotesite/$1
Description:
-
This is a tricky way of virtually running a corporates +
This is a tricky way of virtually running a corporate (external) Internet webserver (www.quux-corp.dom), while actually keeping and maintaining its data on a (internal) Intranet webserver @@ -1634,7 +1634,7 @@ RewriteRule ^/[uge]/([^/]+)/\.www/(.+)\.scgi(.*) ...

which is ugly. Because we have to hard-code both the location of the area and the location of the CGI inside the - hyperlink. When we have to reorganise or area, we spend a + hyperlink. When we have to reorganize the area, we spend a lot of time changing the various hyperlinks.

@@ -1681,7 +1681,7 @@ HREF="*"
How can we transform a static page foo.html into a dynamic variant - foo.cgi in a seemless way, i.e. without notice + foo.cgi in a seamless way, i.e. without notice by the browser/user.
Solution:
@@ -1690,7 +1690,7 @@ HREF="*" We just rewrite the URL to the CGI-script and force the correct MIME-type so it gets really run as a CGI-script. This way a request to /~quux/foo.html - internally leads to the invokation of + internally leads to the invocation of /~quux/foo.cgi.
Configuration file when compiling the Apache webserver. This way it gets called _before_ mod_proxy. Then we configure the following for a - host-dependend deny... + host-dependent deny...
@@ -2182,7 +2182,7 @@ RewriteRule !^http://[^/.]\.mydomain.com.* - [F]
-

...and this one for a user@host-dependend deny:

+

...and this one for a user@host-dependent deny:

-- 2.40.0