From: Eric Covener <covener@apache.org>
Date: Wed, 4 Apr 2012 01:31:48 +0000 (+0000)
Subject: xform
X-Git-Tag: 2.5.0-alpha~7259
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=3203bcebf699a9f7b70e1caff5f1cc98901efdeb;p=apache

xform

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

diff --git a/docs/manual/mod/mod_ssl.html.en b/docs/manual/mod/mod_ssl.html.en
index 4e87e618ec..960c89c052 100644
--- a/docs/manual/mod/mod_ssl.html.en
+++ b/docs/manual/mod/mod_ssl.html.en
@@ -1815,12 +1815,12 @@ function ::= funcname "<strong>(</strong>" funcargs "<strong>)</strong>"
 <code>funcname</code> the available functions are listed in
 the <a href="../expr.html#functions">ap_expr documentation</a>.</p>
 
-<p>Notice that <em>expression</em> is first parsed into an internal machine
-representation and then evaluated in a second step. Actually, in Global and
-Per-Server Class context <em>expression</em> is parsed at startup time and
-at runtime only the machine representation is executed. For Per-Directory
-context, specifically in a .htaccess context, this is different: here <em>
-expression</em> has to be parsed and immediately executed for every request.</p>
+<p>The <em>expression</em> is parsed into an internal machine
+representation when the configuration is loaded, and then evaluated 
+during request processing.  In .htaccess context, the <em>expression</em> is 
+both parsed and executed each time the .htaccess file is encountered during 
+request processing.</p>
+
 <div class="example"><h3>Example</h3><pre>SSLRequire (    %{SSL_CIPHER} !~ m/^(EXP|NULL)-/                \
             and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd."        \
             and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"}  \