httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From r..@apache.org (Ralf S. Engelschall)
Subject cvs commit: apache-1.3/htdocs/manual/mod mod_rewrite.html
Date Wed, 25 Feb 1998 15:43:00 GMT
rse         98/02/25 07:42:59

  Modified:    htdocs/manual/mod mod_rewrite.html
  Log:
  Ops, we have totally mis-documented the %{LA-U:xxx} and %{LA-F:xxx}
  constructs, thus no one noticed that it can be used to lookup the REMOTE_USER
  variable (one of the mod_rewrite FAQs) even in per-server context.  One just
  has to use %{LA-U:REMOTE_USER} instead of %{REMOTE_USER} there.  Notice that
  %{REMOTE_USER} is also useful, but only for per-dir context.
  
  Revision  Changes    Path
  1.25      +16 -6     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.24
  retrieving revision 1.25
  diff -u -r1.24 -r1.25
  --- mod_rewrite.html	1998/02/24 13:39:08	1.24
  +++ mod_rewrite.html	1998/02/25 15:42:58	1.25
  @@ -774,14 +774,24 @@
   is the value of the HTTP header ``<TT>Proxy-Connection:</TT>''.
   
   <P>
  -<LI>There is the special format: <TT>%{LA-U:url}</TT>
  -for look-aheads like <TT>-U</TT>. This performs a internal sub-request to
  -look-ahead for the final value of <EM>url</EM>.
  +<LI>There is the special format <TT>%{LA-U:variable}</TT> for look-aheads
  +which perform an internal (URL-based) sub-request to determine the final value
  +of <EM>variable</EM>. Use this when you want to use a variable for rewriting
  +which actually is set later in an API phase and thus is not available at the
  +current stage. For instance when you want to rewrite according to the
  +<TT>REMOTE_USER</TT> variable from within the per-server context
  +(<TT>httpd.conf</TT> file) you have to use <TT>%{LA-U:REMOTE_USER}</TT>
  +because this variable is set by the authorization phases which come
  +<EM>after</EM> the URL translation phase where mod_rewrite operates. On the
  +other hand, because mod_rewrite implements its per-directory context
  +(<TT>.htaccess</TT> file) via the Fixup phase of the API and because the
  +authorization phases come <EM>before</EM> this phase, you just can use
  +<TT>%{REMOTE_USER}</TT> there.
   
   <P>
  -<LI>There is the special format: <TT>%{LA-F:file}</TT>
  -for look-aheads like <TT>-F</TT>. This performs a internal sub-request to
  -look-ahead for the final value of <EM>file</EM>.
  +<LI>There is the special format: <TT>%{LA-F:variable}</TT> which perform
an
  +internal (filename-based) sub-request to determine the final value of
  +<EM>variable</EM>. This is the most of the time the same as LA-U above.
   </OL>
   
   <P>
  
  
  

Mime
View raw message