BUG/MINOR: sample: reject a \0 byte in raw string fetches
These fetches return a string pointing to the raw client data, which may
contain a \0 byte, while string consumers rely on it not happening
(
37204a71a). The pattern tree lookup used by case-sensitive "-m str"
matches and by maps stops at this byte, so "user\0admin" matches "user",
while the next hop sees the whole value. A rule based on these fetches
can then be bypassed.
req.ssl_sni and req.rdp_cookie now fail on such a value, and
req.ssl_alpn and req.body_param skip it and report the next one.
Legitimate values never contain a \0.
The reg-test str_embedded_nul.vtc covers it.
This should be backported along with
37204a71a.