You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by co...@apache.org on 2012/04/04 02:57:26 UTC
svn commit: r1309193 - /httpd/httpd/trunk/docs/manual/mod/mod_ssl.xml
Author: covener
Date: Wed Apr 4 00:57:25 2012
New Revision: 1309193
URL: http://svn.apache.org/viewvc?rev=1309193&view=rev
Log:
PR50662: reword the hint about sslrequire expressions being parsed in
htaccess so it doesn't apply non-perdir config.
Modified:
httpd/httpd/trunk/docs/manual/mod/mod_ssl.xml
Modified: httpd/httpd/trunk/docs/manual/mod/mod_ssl.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_ssl.xml?rev=1309193&r1=1309192&r2=1309193&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_ssl.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_ssl.xml Wed Apr 4 00:57:25 2012
@@ -1360,12 +1360,12 @@ href="#envvars">Environment Variables</a
<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>
+
<example><title>Example</title>
<pre>SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)-/ \
and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \