httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: apache-1.3/htdocs/manual/mod mod_rewrite.html
Date Fri, 15 May 1998 09:29:16 GMT
rse         98/05/15 02:29:16

  Modified:    htdocs/manual/mod mod_rewrite.html
  fix typos.
  Revision  Changes    Path
  1.30      +5 -5      apache-1.3/htdocs/manual/mod/mod_rewrite.html
  Index: mod_rewrite.html
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/mod/mod_rewrite.html,v
  retrieving revision 1.29
  retrieving revision 1.30
  diff -u -r1.29 -r1.30
  --- mod_rewrite.html	1998/03/25 08:03:48	1.29
  +++ mod_rewrite.html	1998/05/15 09:29:15	1.30
  @@ -59,7 +59,7 @@
   of rules and an unlimited number of attached rule conditions for each rule to
   provide a really flexible and powerful URL manipulation mechanism.  The URL
   manipulations can depend on various tests, for instance server variables,
  -environment variables, HTTP headers, timestamps and even external database
  +environment variables, HTTP headers, time stamps and even external database
   lookups in various formats can be used to achieve a really granular URL
  @@ -129,7 +129,7 @@
   The internal processing of this module is very complex but needs to be
   explained once even to the average user to avoid common mistakes and to let
  -you exploit its full funtionality. 
  +you exploit its full functionality. 
   <H2><A NAME="InternalAPI">API Phases</A></H2>
  @@ -182,7 +182,7 @@
       manipulations in per-server context are really fast and efficient,
       per-directory rewrites are slow and inefficient due to this chicken and
       egg problem. But on the other hand this is the only way mod_rewrite can
  -    provide (locally restricted) URL manipulatiuons to the avarage user.
  +    provide (locally restricted) URL manipulations to the average user.
  @@ -245,7 +245,7 @@
   <H2><A NAME="InternalBackRefs">Regex Back-Reference Availability</A></H2>
  -One important thing here has to be rememberd: Whenever you
  +One important thing here has to be remembered: Whenever you
   use parenthesis in <EM>Pattern</EM> or in one of the <EM>TestPattern</EM>
   back-reference are internally created which can be used with the
   strings <CODE>$N</CODE> and <CODE>%N</CODE> (see below). And these
  @@ -657,7 +657,7 @@
       post-processing feature: After looking up a value it is parsed according
       to contained ``<CODE>|</CODE>'' characters which have the meaning of ``or''.
       in other words: they indicate a set of alternatives from which the actual
  -    returned value is choosen randomly. Although this sounds crazy and useless, it
  +    returned value is chosen randomly. Although this sounds crazy and useless, it
       was actually designed for load balancing in a reverse proxy situation where
       the looked up values are server names.

View raw message