+ <h4 class="SECT3"><a name="CLIENT-BODY-TAGGER" id="CLIENT-BODY-TAGGER">8.5.6. client-body-tagger</a></h4>
+ <div class="VARIABLELIST">
+ <dl>
+ <dt>Typical use:</dt>
+ <dd>
+ <p>Block requests based on the content of the body data.</p>
+ </dd>
+ <dt>Effect:</dt>
+ <dd>
+ <p>Client request bodies to which this action applies are filtered on-the-fly through the specified
+ regular expression based substitutions, the result is used as tag.</p>
+ </dd>
+ <dt>Type:</dt>
+ <dd>
+ <p>Multi-value.</p>
+ </dd>
+ <dt>Parameter:</dt>
+ <dd>
+ <p>The name of a client-body tagger, as defined in one of the <a href="filter-file.html">filter
+ files</a>.</p>
+ </dd>
+ <dt>Notes:</dt>
+ <dd>
+ <p>Please refer to the <a href="filter-file.html">filter file chapter</a> to learn how to create your own
+ client-body tagger.</p>
+ <p>Client-body taggers are applied to each request body on its own, and as the body isn't modified, each
+ tagger "sees" the original.</p>
+ <p>Chunk-encoded request bodies currently can't be tagged. Request bodies larger than the buffer-limit
+ can't be tagged either.</p>
+ </dd>
+ <dt>Example usage (section):</dt>
+ <dd>
+ <table border="0" bgcolor="#E0E0E0" width="90%">
+ <tr>
+ <td>
+ <pre class="SCREEN"> # Apply blafasel tagger.
+ {+client-body-tagger{blafasel}}
+ /
+
+ # Block request based on the tag created by the blafasel tagger.
+ {+block{Request body contains blafasel}}
+ TAG:^content contains blafasel$</pre>
+ </td>
+ </tr>
+ </table>
+ </dd>
+ </dl>
+ </div>
+ </div>
+ <div class="SECT3">
+ <h4 class="SECT3"><a name="CLIENT-HEADER-TAGGER" id="CLIENT-HEADER-TAGGER">8.5.7. client-header-tagger</a></h4>