diff --git a/doc/modsecurity2-apache-reference.xml b/doc/modsecurity2-apache-reference.xml index 2fca29b4..32213206 100644 --- a/doc/modsecurity2-apache-reference.xml +++ b/doc/modsecurity2-apache-reference.xml @@ -318,14 +318,6 @@ Edit Makefile to configure the correct include path for libxml (for example: INCLUDES=-I/usr/include/libxml2) - - Please consider XML support required. Note that the - ModSecurity Core rules may assume XML support is available - (compiled with -DWITH_LIBXML2). You may have to manually remove - any XML references in the Core rules if you choose not to include - XML support. In future versions of ModSecurity XML support will - be required. - @@ -368,7 +360,17 @@ - If you have compiled Apache yourself you might experience problems + If you have compiled Apache yourself or are compiling for a + distribution, please read the following notes. + + The ModSecurity Core rules may assume XML support is + available (compiled with -DWITH_LIBXML2). You may have to manually + remove any XML references in the Core rules if you choose not to + include XML support. In future versions of ModSecurity XML support + will be required. For these reasons, please consider XML support + required. + + You might experience problems compiling ModSecurity against PCRE. This is because Apache bundles PCRE but this library is also typically provided by the operating system. I would expect most (all) vendor-packaged Apache distributions to be @@ -387,7 +389,7 @@ available only in the Apache source code) and change the include path for ModSecurity (as you did in step 7 above) to point to them. - Do note that if your Apache is using an external PCRE library you + If your Apache is using an external PCRE library you can compile ModSecurity with WITH_PCRE_STUDY defined,which would possibly give you a slight performance edge in regular expression