Adds Status test case with the SecServerSignature being used

If SecServerSignature is used ModSecurity should send the real data, not the
one informed to SecServerSignature.
Originally reported by: Linas

Author: Felipe Zimmerle

tests/regression/misc/20-status-engine.pl renamed to tests/regression/misc/20-status-engine.t

@@ -46,4 +46,28 @@
 		"arg1=val1&arg2=val2",
 	),
 },
+# On and SecServerSignature
+{
+	type => "misc",
+	comment => "SecStatusEngine On using SecServerSignature",
+	conf => qq(
+		SecRuleEngine On
+		SecServerSignature "SpiderServer v0.1a"
+		SecStatusEngine On
+	),
+	match_log => {
+		error => [ qr/ModSecurity: StatusEngine call successfully sent/, 1],
+		-error => [ qr/StatusEngine call: .*SpiderServer v0.1a.*/, 1],
+	},
+	match_response => {
+		status => qr/^200$/,
+	},
+	request => new HTTP::Request(
+		POST => "http://$ENV{SERVER_NAME}:$ENV{SERVER_PORT}/test.txt",
+		[
+			"Content-Type" => "application/x-www-form-urlencoded",
+		],
+		"arg1=val1&arg2=val2",
+	),
+},