Fixed a bug in transformation caching, which would prevent a match in certian cases.

Updated docs on "pass" action to explicitly state that we execute all targets.
This commit is contained in:
brectanus
2008-03-07 20:23:16 +00:00
parent e0f503a133
commit 024e854725
4 changed files with 25 additions and 8 deletions

View File

@@ -4,7 +4,7 @@
Manual</title>
<articleinfo>
<releaseinfo>Version 2.5.1-breach1 (March 05, 2008)</releaseinfo>
<releaseinfo>Version 2.5.1-rc1 (March 07, 2008)</releaseinfo>
<copyright>
<year>2004-2008</year>
@@ -4606,14 +4606,26 @@ SecRule ARGS "attack" <emphasis>multiMatch</emphasis></programlisting>
<para><emphasis>Action Group:</emphasis> Disruptive</para>
<para>Example:</para>
<para>Example1:</para>
<programlisting format="linespecific">SecRule REQUEST_HEADERS:User-Agent "Test" log,<emphasis>pass</emphasis></programlisting>
<para>When using <emphasis>pass</emphasis> with SecRule with multiple
targets, <emphasis>all</emphasis> targets will be processed and
<emphasis>all</emphasis> non-disruptive actions will trigger for
<emphasis>every</emphasis> match found. In the second example the
TX:test target would be incremented by 1 for each matching
argument.</para>
<para>Example2:</para>
<programlisting format="linespecific">SecRule ARGS "test" log,<emphasis>pass</emphasis>,setvar:TX.test=+1</programlisting>
<para><emphasis>Note</emphasis></para>
<para>Transaction will not be interrupted but it will be logged (unless
logging has been suppressed).</para>
<para>The transaction will not be interrupted but a log will be
generated for each matching target (unless logging has been
suppressed).</para>
</section>
<section>
@@ -6053,4 +6065,4 @@ Server: Apache/2.x.x
</section>
</section>
</section>
</article>
</article>