github_mirrors/ModSecurity
3
0
Fork 1
mirror of https://github.com/owasp-modsecurity/ModSecurity.git synced 2026-01-16 00:17:11 +03:00
Code Issues Packages Projects Releases Wiki Activity

Adjust example rule for INBOUND_DATA_ERROR

Martin Vierula
2022-11-24 05:18:36 -08:00
parent 3960d1cb32
commit bf0f689198
3 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Reference-Manual-(v2.x)-Variables.mediawiki

@@ -168,7 +168,7 @@ This variable will be set to 1 when the request body size is above the setting c
The best way to use this variable is as in the example below: The best way to use this variable is as in the example below:
<code>SecRule INBOUND_DATA_ERROR "@eq 1" "phase:1,id:24,t:none,log,pass,msg:'Request Body Larger than SecRequestBodyLimit Setting'"</code> <code>SecRule INBOUND_DATA_ERROR "@eq 1" "phase:2,id:24,t:none,log,pass,msg:'Request Body Larger than SecRequestBodyLimit Setting'"</code>
== MATCHED_VAR == == MATCHED_VAR ==
This variable holds the value of the most-recently matched variable. It is similar to the TX:0, but it is automatically supported by all operators and there is no need to specify the capture action. This variable holds the value of the most-recently matched variable. It is similar to the TX:0, but it is automatically supported by all operators and there is no need to specify the capture action.

2
Reference-Manual-(v2.x).mediawiki

@@ -2101,7 +2101,7 @@ This variable will be set to 1 when the request body size is above the setting c
The best way to use this variable is as in the example below: The best way to use this variable is as in the example below:
<code>SecRule INBOUND_DATA_ERROR "@eq 1" "phase:1,id:24,t:none,log,pass,msg:'Request Body Larger than SecRequestBodyLimit Setting'"</code> <code>SecRule INBOUND_DATA_ERROR "@eq 1" "phase:2,id:24,t:none,log,pass,msg:'Request Body Larger than SecRequestBodyLimit Setting'"</code>
== MATCHED_VAR == == MATCHED_VAR ==
This variable holds the value of the most-recently matched variable. It is similar to the TX:0, but it is automatically supported by all operators and there is no need to specify the capture action. This variable holds the value of the most-recently matched variable. It is similar to the TX:0, but it is automatically supported by all operators and there is no need to specify the capture action.

2
Reference-Manual-(v3.x).mediawiki

@@ -1261,7 +1261,7 @@ This variable will be set to 1 when the request body size is above the setting c
The best way to use this variable is as in the example below: The best way to use this variable is as in the example below:
<code>SecRule INBOUND_DATA_ERROR "@eq 1" "phase:1,id:24,t:none,log,pass,msg:'Request Body Larger than SecRequestBodyLimit Setting'"</code> <code>SecRule INBOUND_DATA_ERROR "@eq 1" "phase:2,id:24,t:none,log,pass,msg:'Request Body Larger than SecRequestBodyLimit Setting'"</code>
== MATCHED_VAR == == MATCHED_VAR ==
This variable holds the value of the most-recently matched variable. It is similar to the TX:0, but it is automatically supported by all operators and there is no need to specify the capture action. This variable holds the value of the most-recently matched variable. It is similar to the TX:0, but it is automatically supported by all operators and there is no need to specify the capture action.