MINOR: checks: add rbinary expect match type
The rbinary match works similarly to the rstring match type, however the
received data is rewritten as hex-string before the match operation is
done.
This allows using regexes on binary content even with the POSIX regex
engine.
[Cf: I slightly updated the patch. mem2hex function was removed and dump_binary
is used instead.]
diff --git a/doc/configuration.txt b/doc/configuration.txt
index df09280..09f4b66 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -9865,8 +9865,8 @@
the evaluation result is always conclusive.
<match> is a keyword indicating how to look for a specific pattern in the
- response. The keyword may be one of "string", "rstring" or
- binary.
+ response. The keyword may be one of "string", "rstring", "binary" or
+ "rbinary".
The keyword may be preceded by an exclamation mark ("!") to negate
the match. Spaces are allowed between the exclamation mark and the
keyword. See below for more details on the supported keywords.
@@ -9904,6 +9904,15 @@
this exact hexadecimal string.
Purpose is to match data on binary protocols.
+ rbinary <regex> : test a regular expression on the response buffer, like
+ "rstring". However, the response buffer is transformed
+ into its hexadecimal form, including NUL-bytes. This
+ allows using all regex engines to match any binary
+ content. The hexadecimal transformation takes twice the
+ size of the original response. As such, the expected
+ pattern should work on at-most half the response buffer
+ size.
+
It is important to note that the responses will be limited to a certain size
defined by the global "tune.chksize" option, which defaults to 16384 bytes.
Thus, too large responses may not contain the mandatory pattern when using