At this stage we have to have the mapping of Apache configuration with the ModSecurity parser, making the version 3 fully compatible with version 2. Is not longer expected to have `ugly' parser errors or memory leaks while loading the configuration.
It will be considerable Beta ready whenever we have ModSecurity regression tests passing 100%; Notice that here we meant to have regressions tests for v2 and for version 3, in additional to the FTW with test-beds generated on v2.
List view
0 issues of 6 selected
- Status: Closed (completed).#50 In owasp-modsecurity/ModSecurity-apache;
- Status: Closed (completed).#46 In owasp-modsecurity/ModSecurity-apache;
- Status: Closed (completed).#58 In owasp-modsecurity/ModSecurity-apache;
- Status: Closed (abandoned).owasp-modsecurity/ModSecurity-apachenumber 21#21 In owasp-modsecurity/ModSecurity-apache;
- Status: Closed (abandoned).owasp-modsecurity/ModSecurity-apachenumber 22#22 In owasp-modsecurity/ModSecurity-apache;
- Status: Closed (abandoned).owasp-modsecurity/ModSecurity-apachenumber 20#20 In owasp-modsecurity/ModSecurity-apache;