Actions
Actions to perform in response to traffic analysis
Last updated
Actions to perform in response to traffic analysis
Last updated
At various stages in the traffic filtering process, Reblaze can execute an action according to the characteristics of the request. These actions are defined within Actions.
Out of the box, Reblaze includes several default Actions for admins to select. Additional ones can also be defined.
Actions are available at various stages of the traffic filtering process, e.g. Global Filters, Rate Limit Rules, ACL Profiles, and Content Filter Profiles.
As shown in the diagram below, different types of Actions can occur at various stages. An Action can terminate the processing of a request by blocking it, but other Actions (Skip, Challenge, and Monitor) are available as well, with different outcomes. See the description below of the Type parameter.
The main page lists all current Actions.
The administration (addition/deletion/editing/versioning) of Actions follows the conventions described here.
An Action consists of the following:
The Type of the action
Additional Type-specific parameters
Tag(s) to attach to requests that triggered this action
General parameters for administration
A name for this Action, to be used within the Reblaze interface.
Information about this Action, for use within the interface.
This parameter will be one of the values below.
Skip
Block
Adds the tag(s) to the request, and sends a response to the user with the defined Response headers, Status code, and Content.
Challenge
Interactive Challenge
Monitor
Sometimes Reblaze must choose one of several potential Actions. For example, when a request matches the conditions for multiple Global Filters, each Filter will include an Action. The system must execute the highest-priority one.
The priority hierarchy is, from highest to lowest:
Skip
Block
Challenges (bot and/or interactive)
Monitor
A list of one or more tags, separated by spaces. When this Action is triggered, these tags will appear in the traffic logs.
The status code returned to the user. (Optional: only applies to those responses that return a code.)
A list of header(s) to add to the response that is sent to the user, specified as the header name and its value. Example: content-type and text/html.
The response sent to the user, of the appropriate format and type. Example: if there is a Request Header of content-type and text/html, then this should begin with <html> and end with </html>.
Adds the tag(s) to the request, then skips the remainder of the traffic evaluation process (similar to the Bypass option in ). Note that any Response phase will still be executed (as they are not part of the evaluation process).
Adds the tag(s) to the request, and issues a to verify that the user is human.
Adds the tag(s) to the request, and issues an to verify that the user is human.
Adds the tag(s) to the request, and continues to the next stage of without responding to the user. Admins can also define Request headers to add to the request as it is passed upstream.
