- The "merging" optimization in mod_setenvif did not deal with

  SetEnvIfNoCase properly; and it used strcmp() to compare header
  names when it should use strcasecmp().

- Change the merging optimization so that it only considers the most
  recent setenvif for merging.  This means that mod_setenvif will
  consider all directives in the order they appear in the config file.

- Document that mod_setenvif considers directives in the order they
  appear, and give an example use.

- Perform more comparisons at compile-time in order to speed up things
  at compile-time.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@80545 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/mod/mod_setenvif.html b/docs/manual/mod/mod_setenvif.html
index cb80be0e38af7577a3446217bf473f840f0ac8f7..46a91d5db8520cb17c4fb5f601dc717d30f3f1b7 100644 (file)
--- a/docs/manual/mod/mod_setenvif.html
+++ b/docs/manual/mod/mod_setenvif.html
@@ -26,6 +26,16 @@
   regular expressions you specify.  These envariables can be used by
   other parts of the server to make decisions about actions to be taken.
   </P>
+  <p>The directives are considered in the order they appear in the
+  configuration files.  So more complex sequences can be used, such
+  as this example, which sets <code>netscape</code> if the browser
+  is mozilla but not MSIE.
+  <blockquote><pre>
+  BrowserMatch ^Mozilla netscape
+  BrowserMatch MSIE !netscape
+  </pre></blockquote>
+  </p>
+
   <H2>Directives</H2>
   <UL>
    <LI><A HREF="#BrowserMatch">BrowserMatch</A>