httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From r..@hyperreal.org
Subject cvs commit: apache-1.3/htdocs/manual/mod mod_rewrite.html
Date Thu, 22 Oct 1998 12:02:29 GMT
rse         98/10/22 05:02:29

  Modified:    htdocs/manual/mod mod_rewrite.html
  Log:
  Fix a few bugs in the mod_rewrite documentation by the
  help of some hints from Adam M Donahue <amd0978@acf3.nyu.edu>.
  
  Revision  Changes    Path
  1.39      +8 -8      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.38
  retrieving revision 1.39
  diff -u -r1.38 -r1.39
  --- mod_rewrite.html	1998/09/17 14:14:57	1.38
  +++ mod_rewrite.html	1998/10/22 12:02:27	1.39
  @@ -248,21 +248,21 @@
   continues with the next rule. If the <EM>Pattern</EM> matched, mod_rewrite
   looks for corresponding rule conditions. If none are present, it just
   substitutes the URL with a new value which is constructed from the string
  -<EM>Substitution</EM> and goes on with its rule-looping. But if conditions
But
  +<EM>Substitution</EM> and goes on with its rule-looping. But
   if conditions exists, it starts an inner loop for processing them in order
   they are listed. For conditions the logic is different: We don't match a
   pattern against the current URL. Instead we first create a string
  -<EM>TestString</EM> by expanding variables, back-references, map lookups, <EM>etc.</EM>
  -and then we try to match <EM>TestPattern</EM> against it. If the pattern
  -doesn't match, the complete set of conditions and the corresponding rule fails.
  -If the pattern matches, then the next condition is processed until no more
  -condition is available. If all conditions matched processing is continued with
  -the substitution of the URL with <EM>Substitution</EM>.
  +<EM>TestString</EM> by expanding variables, back-references, map lookups,
  +<EM>etc.</EM> and then we try to match <EM>CondPattern</EM> against
it. If the
  +pattern doesn't match, the complete set of conditions and the corresponding
  +rule fails.  If the pattern matches, then the next condition is processed
  +until no more condition is available. If all conditions matched processing is
  +continued with the substitution of the URL with <EM>Substitution</EM>.
   
   <H2><A NAME="InternalBackRefs">Regex Back-Reference Availability</A></H2>
   
   One important thing here has to be remembered: Whenever you
  -use parenthesis in <EM>Pattern</EM> or in one of the <EM>TestPattern</EM>
  +use parenthesis in <EM>Pattern</EM> or in one of the <EM>CondPattern</EM>
   back-reference are internally created which can be used with the
   strings <CODE>$N</CODE> and <CODE>%N</CODE> (see below). And these
   are available for creating the strings <EM>Substitution</EM> and
  
  
  

Mime
View raw message