httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rodent of Unusual Size <c...@hyperreal.org>
Subject cvs commit: apachen/htdocs/manual/mod mod_include.html
Date Thu, 28 Aug 1997 15:24:10 GMT
coar        97/08/28 08:24:09

  Modified:    htdocs/manual new_features_1_3.html
               htdocs/manual/mod mod_include.html
  Log:
  	The long-awaited doc update for the conditional SSI enhancements
  	(including some HTML cleanup), and some additional items for the
  	new-for-1.3 page.
  
  PR:		41
  
  Revision  Changes    Path
  1.20      +39 -0     apachen/htdocs/manual/new_features_1_3.html
  
  Index: new_features_1_3.html
  ===================================================================
  RCS file: /export/home/cvs/apachen/htdocs/manual/new_features_1_3.html,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- new_features_1_3.html	1997/08/18 07:26:26	1.19
  +++ new_features_1_3.html	1997/08/28 15:24:05	1.20
  @@ -29,6 +29,45 @@
   1.3</a> has the following specific new user features:</p>
   
   <ul>
  + <LI><A
  +      HREF="mod/mod_setenvif.html"
  +     ><STRONG>Enhanced Conditional Setting of Environment Variables</STRONG></A>
  +  <BR>
  +  The
  +  <A
  +   HREF="mod/mod_setenvif.html#BrowserMatch"
  +  ><SAMP>BrowserMatch*</SAMP></A>
  +  directives of Apache 1.2 have been joined by some more powerful
  +  brethren:
  +  <A
  +   HREF="mod/mod_setenvif.html#SetEnvIf"
  +  ><SAMP>SetEnvIf</SAMP></A>
  +  and
  +  <A
  +   HREF="mod/mod_setenvif.html#SetEnvIfNoCase"
  +  ><SAMP>SetEnvIfNoCase</SAMP></A>.  These allow you to set environment
  +  variables for server and CGI use based upon all <EM>sorts</EM> of
  +  attributes of the request.
  + </LI>
  + <LI><STRONG>Better Logging for Proxy Connect Errors</STRONG>
  +  <BR>
  +  In Apache 1.2 and earlier, when the proxy had difficulty connecting to
  +  a system it would log the error but no details.  It now includes the
  +  IP address and port to which it couldn't connect.
  + </LI>
  + <LI><A
  +      HREF="mod/mod_include.html#flowctrl"
  +     ><STRONG>Enhanced SSI String Comparisons</STRONG></A>
  +  <BR>
  +  The string-based server-side include (SSI) flow-control directives
  +  provided by
  +  <A
  +   HREF="mod/mod_include.html"
  +  ><SAMP>mod_include</SAMP></A>
  +  now include comparison for less-than (&lt;), less-than-or-equal
  +  (&lt;=), greater-than (&gt;), and greater-than-or-equal (&gt;=).
  +  Previously comparisons could only be made for equality or inequality.
  + </LI>
   <LI><A
        HREF="sourcereorg.html"
       ><STRONG>Re-organised Sources</STRONG></A>
  
  
  
  1.16      +42 -33    apachen/htdocs/manual/mod/mod_include.html
  
  Index: mod_include.html
  ===================================================================
  RCS file: /export/home/cvs/apachen/htdocs/manual/mod/mod_include.html,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -r1.15 -r1.16
  --- mod_include.html	1997/07/06 17:19:17	1.15
  +++ mod_include.html	1997/08/28 15:24:07	1.16
  @@ -267,62 +267,71 @@
       &lt;!--#endif --&gt;
   </PRE>
   
  -<H2>Flow Control Elements</H2>
  +<H2><A NAME="flowctrl">Flow Control Elements</A></H2>
   
   These are available in Apache 1.2 and above.  The basic flow control
   elements are:
   
   <PRE>
  -    &lt;!--#if expr="<I>test_condition</I>" --&gt;
  -    &lt;!--#elif expr="<I>test_condition</I>" --&gt;
  +    &lt;!--#if expr="<EM>test_condition</EM>" --&gt;
  +    &lt;!--#elif expr="<EM>test_condition</EM>" --&gt;
       &lt;!--#else --&gt;
       &lt;!--#endif --&gt;
   </PRE>
   
  -<P> The <B><CODE>if</CODE></B> element works like an
  +<P> The <STRONG><CODE>if</CODE></STRONG> element works like
an
       if statement in a programming language.  The test condition
       is evaluated and if the result is true, then the text until
  -    the next <B><CODE>elif</CODE></B>, <B><CODE>else</CODE></B>.
  -    or <B><CODE>endif</CODE></B> element is included in the
  +    the next <STRONG><CODE>elif</CODE></STRONG>, <STRONG><CODE>else</CODE></STRONG>.
  +    or <STRONG><CODE>endif</CODE></STRONG> element is included
in the
       output stream.
   
  -<P> The <B><CODE>elif</CODE></B> or <B><CODE>else</CODE></B>
  +<P> The <STRONG><CODE>elif</CODE></STRONG> or <STRONG><CODE>else</CODE></STRONG>
       statements are be used the put text into the output stream
       if the original test_condition was false.  These elements
       are optional.
   
  -<P> The <B><CODE>endif</CODE></B> element ends the
  -    <B><CODE>if</CODE></B> element and is required.
  +<P> The <STRONG><CODE>endif</CODE></STRONG> element ends
the
  +    <STRONG><CODE>if</CODE></STRONG> element and is required.
   
  -<P> <I>test_condition</I> is one of the following:
  +<P> <EM>test_condition</EM> is one of the following:
   
   <DL>
   
  -<DT><I>string</I><DD>true if <I>string</I> is not empty
  +<DT><EM>string</EM><DD>true if <EM>string</EM> is not
empty
   
  -<DT><I>string1</I> = <I>string2</I><BR>
  -    <I>string1</I> != <I>string2</I>
  +<DT><EM>string1</EM> = <EM>string2</EM>
  +    <BR>
  +    <EM>string1</EM> != <EM>string2</EM>
  +    <BR>
  +    <EM>string1</EM> &lt; <EM>string2</EM>
  +    <BR>
  +    <EM>string1</EM> &lt;= <EM>string2</EM>
  +    <BR>
  +    <EM>string1</EM> &gt; <EM>string2</EM>
  +    <BR>
  +    <EM>string1</EM> &gt;= <EM>string2</EM>
   
  -<DD>Compare string1 with string 2.  If string2 has the form <I>/string/</I>
  -    than it is compared as a regular expression.
  +<DD>Compare string1 with string 2.  If string2 has the form <EM>/string/</EM>
  +    then it is compared as a regular expression.
       Regular expressions have the same syntax as those found in the
  -    Unix egrep command.
  +    Unix <SAMP>egrep</SAMP> command.
   
  -<DT>( <I>test_condition</I> )
  -        <DD>true if <I>test_condition</I> is true
  -<DT>! <I>test_condition</I>
  -        <DD>true if <I>test_condition</I> is false
  -<DT><I>test_condition1</I> && <I>test_condition2</I>
  -        <DD>true if both <I>test_condition1</I> and
  -        <I>test_condition2</I> are true
  -<DT><I>test_condition1</I> || <I>test_condition2</I>
  -        <DD>true if either <I>test_condition1</I> or
  -        <I>test_condition2</I> is true
  +<DT>( <EM>test_condition</EM> )
  +        <DD>true if <EM>test_condition</EM> is true
  +<DT>! <EM>test_condition</EM>
  +        <DD>true if <EM>test_condition</EM> is false
  +<DT><EM>test_condition1</EM> && <EM>test_condition2</EM>
  +        <DD>true if both <EM>test_condition1</EM> and
  +        <EM>test_condition2</EM> are true
  +<DT><EM>test_condition1</EM> || <EM>test_condition2</EM>
  +        <DD>true if either <EM>test_condition1</EM> or
  +        <EM>test_condition2</EM> is true
   </DL>
   
  -<P> "<I>=</I>" and "<I>!=</I>" bind more tightly than "<I>&&</I>"
and
  -    "<I>||</I>".
  -    "<I>!</I>" binds most tightly.  Thus, the following are equivalent:
  +<P> "<EM>=</EM>" and "<EM>!=</EM>" bind more tightly than
"<EM>&&</EM>" and
  +    "<EM>||</EM>".
  +    "<EM>!</EM>" binds most tightly.  Thus, the following are equivalent:
   
   <PRE>
       &lt;!--#if expr="$a = test1 && $b = test2" --&gt;
  @@ -330,15 +339,15 @@
   </PRE>
   
   <P> Anything that's not recognized as a variable or an operator is
  -    treated as a string.  Strings can also be quoted: <I>'string'</I>.
  +    treated as a string.  Strings can also be quoted: <EM>'string'</EM>.
       Unquoted strings can't contain whitespace (blanks and tabs)
       because it is used to separate tokens such as variables.  If
       multiple strings are found in a row, they are concatenated using
       blanks.  So,
   
   <PRE>
  -     <I>string1    string2</I>  results in <I>string1 string2</I>
  -    <I>'string1    string2'</I> results in <I>string1    string2</I>
  +     <EM>string1    string2</EM>  results in <EM>string1 string2</EM>
  +    <EM>'string1    string2'</EM> results in <EM>string1    string2</EM>
   </PRE>
   
   <hr>
  @@ -374,7 +383,7 @@
   last modified time of the file. If it is not set, then no last-modified date
   is sent. Setting this bit allows clients and proxies to cache the result of
   the request.
  -<p><b>Note:</b> you would not want to use this, for example, when you
  +<p><STRONG>Note:</STRONG> you would not want to use this, for example,
when you
   <code>#include</code> a CGI that produces different output on each hit
   (or potentially depends on the hit).
   </dl>
  
  
  

Mime
View raw message