Adding rules in the application profile

To add a new rule, go to the menu and click Settings -> Rules.

Rules can be added to both existing and new branches. They can be created from scratch or based on one of the existing branches.

To add a rule to an existing branch, click Add rule (the button will appear in the pop-up menu on the right after hovering the mouse cursor over the branch description line). You can also perform this operation on the rule page of this branch.

If necessary, it is possible to modify the branch to which a rule will be added. For this, click on the If clause in the rule-adding form and make changes in the branch description conditions. If such a branch didn't exist before, it will appear on the screen, and the application structure view will be updated.

Branch description

A branch definition consists of a set of conditions for various parameters of an HTTP request, which must fulfill these conditions, otherwise, the rules pertaining to this branch will not be applied. Each line in the If section of the rule-adding form refers to a separate condition composed of three fields: point, type and comparison argument. The rules described in the branch are applied to the request only if all the conditions are fulfilled.

The point field indicates which parameter value should be extracted from the request for comparison. At present, not all the points which can be analyzed by the filter node, are supported.

  • instance — application ID.
  • proto — HTTP protocol version (1.0, 1.1, 2.0, ...).
  • scheme — http or https.
  • url - full URL of the request in the same form as it was passed in the first line of the HTTP request.
  • path, action_name, action_ext — URL elements. The details are provided in the request analysis description.
  • get — GET parameters in the request.
  • header — request headers.

Condition categories:

  • equal — point value must match precisely with the comparison argument.
  • regex — point value must match the regular expression. Note that the system uses a limited subset of the regular expression syntax.
  • absent — the request shouldn't contain the designated point. In this case, the comparison argument is not used.


The added request processing rule is described in the Then section.

The following rules are supported:

results matching ""

    No results matching ""