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 +
  • 6 Installation for NGINX + +
  • 6 Installation for +class="tocnumber">7 Installation for Microsoft IIS
  • 7 Configuration +class="tocnumber">8 Configuration Directives
  • 8 Processing Phases +class="tocnumber">9 Processing Phases
  • -
  • 9 +
  • 10 Variables
  • 10 Transformation +class="tocnumber">11 Transformation functions
  • -
  • 11 +
  • 12 Actions
  • -
  • 12 +
  • 13 Operators
  • 13 Macro Expansion
  • +class="tocnumber">14 Macro Expansion
  • 14 Persistant Storage
  • +class="tocnumber">15 Persistant Storage
  • 15 Miscellaneous Topics +class="tocnumber">16 Miscellaneous Topics
  • 16 A Recommended Base + class="tocnumber">17 A Recommended Base Configuration
  • @@ -1274,6 +1288,45 @@ must run more than one script per transaction. has been moved to phase 2 hook, if you want to play around it use this option. +

    Installation for NGINX

    +

    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. +

    +

    Manually Installing ModSecurity Module on NGINX

    +

    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 +

    +

    Installation Steps

    +

    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. +

    Installation for Microsoft IIS

    @@ -1306,7 +1359,7 @@ class="external free" title="http://www.microsoft.com/en-us/download/details.aspx?id=14632" rel="nofollow">http://www.microsoft.com/en-us/download/details.aspx?id=14632 -

    Installation Steps

    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.
  • ruleUpdateTargetById - This is deprecated and will be removed from the code. Use ruleRemoveTargetById for per-request exceptions. -
  • ruleRemoveTargetById +
  • ruleRemoveTargetById - since this action is used to just + remove targets, users don't need to use the char ! before the +target list.
  • ruleRemoveByMsg
  • encryptionEngine
  • encryptionEnforcement @@ -6293,7 +6348,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}, \ IH %{MULTIPART_INVALID_HEADER_FOLDING}, \ IH %{MULTIPART_FILE_LIMIT_EXCEEDED}'" @@ -6431,13 +6486,13 @@ SecCookieFormat 0 - + @@ -6547,7 +6602,7 @@ pages
  • href="http://sourceforge.net/apps/mediawiki/mod-security/index.php?title=Reference_Manual&printable=yes&printable=yes" rel="alternate" title="Printable version of this page [alt-shift-p]" accesskey="p">Printable version @@ -6559,15 +6614,15 @@ href="http://sourceforge.net/apps/mediawiki/mod-security/index.php?title=Referen src="Reference_Manual_files/poweredby_mediawiki_88x31.png" alt="Powered by MediaWiki"> - +