Expand doc desription re: SecDefaultAction and phase

Martin Vierula
2023-03-13 07:20:38 -07:00
parent 4ecb8c1ddf
commit 55dc14d57f
4 changed files with 6 additions and 6 deletions

@@ -463,7 +463,7 @@ SecRule REQUEST_HEADERS:User-Agent "Test" "log,pause:5000,id:125"
; Warning : This feature can be of limited benefit for slowing down brute force authentication attacks, but use with care. If you are under a denial of service attack, the pause feature may make matters worse, as it will cause an entire Apache worker (process or thread, depending on the deployment mode) to sit idle until the pause is completed. ; Warning : This feature can be of limited benefit for slowing down brute force authentication attacks, but use with care. If you are under a denial of service attack, the pause feature may make matters worse, as it will cause an entire Apache worker (process or thread, depending on the deployment mode) to sit idle until the pause is completed.
== phase == == phase ==
'''Description''': Places the rule or chain into one of five available processing phases. It can also be used in SecDefaultAction to establish the rule defaults. '''Description''': Places the rule or chain into one of five available processing phases. It can also be used in SecDefaultAction to establish the rule defaults for that phase.
'''Action Group:''' Meta-data '''Action Group:''' Meta-data

@@ -422,7 +422,7 @@ The possible values for the debug log level are:
*9: log everything, including very detailed debugging information *9: log everything, including very detailed debugging information
== SecDefaultAction == == SecDefaultAction ==
'''Description''': Defines the default list of actions, which will be inherited by the rules in the same configuration context. '''Description''': Defines the default list of actions for a particular phase, which will be inherited by the rules in the same phase and in the same configuration context.
'''Syntax:''' <code>SecDefaultAction "action1,action2,action3“ </code> '''Syntax:''' <code>SecDefaultAction "action1,action2,action3“ </code>

@@ -653,7 +653,7 @@ The possible values for the debug log level are:
*9: log everything, including very detailed debugging information *9: log everything, including very detailed debugging information
== SecDefaultAction == == SecDefaultAction ==
'''Description''': Defines the default list of actions, which will be inherited by the rules in the same configuration context. '''Description''': Defines the default list of actions for a particular phase, which will be inherited by the rules in the same phase and in the same configuration context.
'''Syntax:''' <code>SecDefaultAction "action1,action2,action3“ </code> '''Syntax:''' <code>SecDefaultAction "action1,action2,action3“ </code>
@@ -3468,7 +3468,7 @@ SecRule REQUEST_HEADERS:User-Agent "Test" "log,pause:5000,id:125"
; Warning : This feature can be of limited benefit for slowing down brute force authentication attacks, but use with care. If you are under a denial of service attack, the pause feature may make matters worse, as it will cause an entire Apache worker (process or thread, depending on the deployment mode) to sit idle until the pause is completed. ; Warning : This feature can be of limited benefit for slowing down brute force authentication attacks, but use with care. If you are under a denial of service attack, the pause feature may make matters worse, as it will cause an entire Apache worker (process or thread, depending on the deployment mode) to sit idle until the pause is completed.
== phase == == phase ==
'''Description''': Places the rule or chain into one of five available processing phases. It can also be used in SecDefaultAction to establish the rule defaults. '''Description''': Places the rule or chain into one of five available processing phases. It can also be used in SecDefaultAction to establish the rule defaults for that phase.
'''Action Group:''' Meta-data '''Action Group:''' Meta-data

@@ -421,7 +421,7 @@ The possible values for the debug log level are:
*9: log everything, including very detailed debugging information *9: log everything, including very detailed debugging information
== SecDefaultAction == == SecDefaultAction ==
'''Description''': Defines the default list of actions, which will be inherited by the rules in the same configuration context. '''Description''': Defines the default list of actions for a particular phase, which will be inherited by the rules in the same phase and in the same configuration context.
'''Syntax:''' <code>SecDefaultAction "action1,action2,action3“ </code> '''Syntax:''' <code>SecDefaultAction "action1,action2,action3“ </code>
@@ -2344,7 +2344,7 @@ SecRule ARGS "test" "phase:2,log,pass,setvar:TX.test=+1,id:124"
''Not supported in v3''' ''Not supported in v3'''
== phase == == phase ==
'''Description''': Places the rule or chain into one of five available processing phases. It can also be used in SecDefaultAction to establish the rule defaults. '''Description''': Places the rule or chain into one of five available processing phases. It can also be used in SecDefaultAction to establish the rule defaults for that phase.
'''Action Group:''' Meta-data '''Action Group:''' Meta-data