Skip to content

Create new API call to allow users to create directory configs in apr me... #619

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

thehelix112
Copy link

This adds a standalone library API call that allows users to create directory_config objects in apr memory pools they control. This, coupled with #618 aims to allow users to re-configure modsecurity on the fly without effectively leaking memory.

Felipe Zimmerle and others added 24 commits December 4, 2013 06:19
Vera++ and ccpcheck are not outputing to the stderr instead stdout
allowing the buildbot to extract some numbers about it.
WarningCountingShellCommand allow us to have some measurements on
the buildbot waterfall.
No need to use a 3rd description on the quality check scripts.
Stderr is now redirected to stdout and filtered as needed.
Avoding conflicts with the standalone implementation
Makefile.in is recommended to be in the repository whenever it is edit manually,
in our case the automatically generated Makefile.in is ok.
- pcre from 8.30 to 8.33
- zlib from 1.2.7 to 1.2.8
- libxml2 from 2.7.7 to 2.9.1
- curl from 7.24 to 7.33.0
Build scripts was creating links allowing the project to
be loaded into Visual Studio without care about the
dependencies versions. Sometimes windows refuse to delete
those links leading the script to fail. This patch
moves the sources directories instead of create links
to it.
The unit tests was not working due to lack update. This patch adds
the necessary stuff to have it work again.
Changed to reduce the number of possible fails during
Build Bot compilation.
Changes in httpd.conf.in to get it working with apache 2.4
This is needed to get it compiled with VS2011 on Windows8
The nginx config file was looking for depedencies by its own,
by doing that it was ignoring the options that were passed to
configure script. This commit deletes this config file and adds
a meta-config which is populated by configure whenever the
standalone-module is enabled.
Now using one file per line (sorted). This is the better way
to handle it, since it reduces the possibility of merge conflicts.
Contains the CHANGES of the 2.7.6 release.
Release 2.7.6 ready.
… memory pools they control, rather than the default global pool every time.
@thehelix112
Copy link
Author

Hey Filipe,

Any progress with this pull-request? Is there anything that I need to address or improve?
Thanks,

Dave

@zimmerle zimmerle closed this Mar 20, 2014
@zimmerle zimmerle added this to the testing milestones milestone Mar 27, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants