github_mirrors/ModSecurity
3
0
Fork 1
mirror of https://github.com/owasp-modsecurity/ModSecurity.git synced 2025-09-29 19:24:29 +03:00
Code Issues Packages Projects Releases Wiki Activity

Fix test issue-1831.json on LMDB

Browse Source 
When LMDB is enabled, ModSecurity stores its persistent variables in
"./modsec-shared-collections" file. Since this file wasn't cleared between
tests, tests behaved differently on "in-memory per-process" and LMDB backend.

This test never worked in LMDB configuration. It hasn't been discovered
until now because Travis CI didn't test LMDB configuration when test was
introduced.
This commit is contained in:
WGH
2019-01-25 21:08:34 +03:00
committed by Felipe Zimmerle
parent 37cf60b8d2
commit bd6a02d69b
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
test/regression/regression.cc
View File

@@ -15,6 +15,8 @@
#include <string.h> #include <string.h>
#include <unistd.h>
#include <ctime> #include <ctime>
#include <iostream> #include <iostream>
#include <string> #include <string>
@@ -136,6 +138,12 @@ void perform_unit_test(ModSecurityTest<RegressionTest> *test,
continue; continue;
} }
#ifdef WITH_LMDB
// some tests (e.g. issue-1831.json) don't like it when data persists between runs
unlink("./modsec-shared-collections");
unlink("./modsec-shared-collections-lock");
#endif
modsec = new modsecurity::ModSecurity(); modsec = new modsecurity::ModSecurity();
modsec->setConnectorInformation("ModSecurity-regression v0.0.1-alpha" \ modsec->setConnectorInformation("ModSecurity-regression v0.0.1-alpha" \
" (ModSecurity regression test utility)"); " (ModSecurity regression test utility)");