You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/docs/seclang/actions.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: "Actions"
3
3
description: "Actions available in Coraza"
4
4
lead: "The action of a rule defines how to handle HTTP requests that have matched one or more rule conditions."
5
5
date: 2020-10-06T08:48:57+00:00
6
-
lastmod: "2026-01-15T14:26:37-03:00"
6
+
lastmod: "2026-01-15T16:50:59-03:00"
7
7
draft: false
8
8
images: []
9
9
menu:
@@ -28,7 +28,6 @@ Disruptive actions will NOT be executed if the `SecRuleEngine` is set to `Detect
28
28
***Meta-data actions** - used to provide more information about rules. Examples include id, rev, severity and msg.
29
29
***Data actions** - Not really actions, these are mere containers that hold data used by other actions. For example, the status action holds the status that will be used for blocking (if it takes place).
30
30
31
-
32
31
## allow
33
32
34
33
**Description**: Stops rule processing on a successful match and allows a transaction to be proceed.allow will affect the entire transaction.
Copy file name to clipboardExpand all lines: tools/actionsgen/template.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,9 @@ toc: true
15
15
16
16
[//]: <>(This file is generated by tools/actionsgen. DO NOT EDIT.)
17
17
18
+
{{ if .PackageDescription -}}
19
+
{{ .PackageDescription }}
20
+
{{ else -}}
18
21
Actions are defined as part of a `SecRule` or as parameter for `SecAction` or `SecDefaultAction`. A rule can have no or several actions which need to be separated by a comma.
19
22
20
23
Actions can be categorized by how they affect overall processing:
@@ -27,6 +30,7 @@ Disruptive actions will NOT be executed if the `SecRuleEngine` is set to `Detect
27
30
***Flow actions** - These actions affect the rule flow (for example skip or skipAfter).
28
31
***Meta-data actions** - used to provide more information about rules. Examples include id, rev, severity and msg.
29
32
***Data actions** - Not really actions, these are mere containers that hold data used by other actions. For example, the status action holds the status that will be used for blocking (if it takes place).
0 commit comments