List view

• v2 conf style

  This milestone is about having a configuration style in the same fashion as version 2. Ideally the user will change the version 2 by version 3 and reload Apache. That should be enough for having the Apache workable with version 3.

  No due date

  •0/1 issues closed
  0% complete1 open0 closed

• Stable version for ModSecurity-apache connector

  Bug fixes and polishing to have it user-ready. No performance issues, and good feedback from the community.

  No due date

  •2/3 issues closed
  66% complete1 open2 closed

• Beta version for ModSecurity-apache connector

  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.

  No due date

  •6/14 issues closed
  42% complete8 open6 closed