diff --git a/doc/Reference_Manual.html b/doc/Reference_Manual.html index 51129213..9072dc8d 100644 --- a/doc/Reference_Manual.html +++ b/doc/Reference_Manual.html @@ -55,7 +55,7 @@ type="text/css"> var wgUserLanguage = "en"; var wgContentLanguage = "en"; var wgBreakFrames = false; - var wgCurRevisionId = 517; + var wgCurRevisionId = 522; var wgVersion = "1.15.1"; var wgEnableAPI = true; var wgEnableWriteAPI = true; @@ -198,669 +198,683 @@ class="tocnumber">5.5.5 Start Apache httpd +
The extensibility model of the nginx server does not include +dynamically loaded modules, thus ModSecurity must be compiled with the +source code of the main server. Since nginx is available on multiple +Unix-based platforms (and also on Windows), for now the recommended way +of obtaining ModSecurity for nginx is compilation in the designated +environment. +
+The first step in obtaining nginx server with built-in ModSecurity +module is building of standalone library containing full ModSecurity +with a set of intermediate API (this layer is a common base for IIS +version, nginx version, and server-less command line version of +ModSecurity). It is recommended to follow the general steps of preparing + build environment for ModSecurity and then follow with two simple +commands +
+1 - Compile standalone module: +
+~/mod_security$ ./configure --enable-standalone-module +~/mod_security$ make ++
2 - Once the standalone library is built successfully, one can follow + with building the nginx server, following the steps from the nginx +build tutorial: +
+~/nginx-1.2.0$ ./configure --add-module=../mod_security/nginx/modsecurity +~/nginx-1.2.0$ make +~/nginx-1.2.0$ sudo make install ++
The last command performs server installation on the local machine, +which can be either customized or omitted with built binaries packaged +or moved to alternative server. +
Download binary package and unzip the content to a separate folder:
@@ -3460,7 +3513,7 @@ MULTIPART_CRLF_LF_LINES. variables is also set to 1: REQBODY_PROCESSOR_ERROR, MULTIPART_BOUNDARY_QUOTED, MULTIPART_BOUNDARY_WHITESPACE, MULTIPART_DATA_BEFORE, MULTIPART_DATA_AFTER, MULTIPART_HEADER_FOLDING, -MULTIPART_LF_LINE, MULTIPART_SEMICOLON_MISSING MULTIPART_INVALID_QUOTING +MULTIPART_LF_LINE, MULTIPART_MISSING_SEMICOLON MULTIPART_INVALID_QUOTING MULTIPART_INVALID_HEADER_FOLDING MULTIPART_FILE_LIMIT_EXCEEDED. Each of these variables covers one unusual (although sometimes legal) aspect of the request body in multipart/form-data format. Your policies should @@ -3481,7 +3534,7 @@ DB %{MULTIPART_DATA_BEFORE}, \ DA %{MULTIPART_DATA_AFTER}, \ HF %{MULTIPART_HEADER_FOLDING}, \ LF %{MULTIPART_LF_LINE}, \ -SM %{MULTIPART_SEMICOLON_MISSING}, \ +SM %{MULTIPART_MISSING_SEMICOLON}, \ IQ %{MULTIPART_INVALID_QUOTING}, \ IQ %{MULTIPART_INVALID_HEADER_FOLDING}, \ FE %{MULTIPART_FILE_LIMIT_EXCEEDED}'" @@ -4691,7 +4744,9 @@ disabling.