Section – Basic Call Verification
Section Basic Call Verification
UI
Description
Apply deny rules to path segments
If enabled each path segment is interpreted as a separate parameter value and the deny rules for parameter values are applied to it. Each parameter value will be assigned to a generic parameter name derived from its position in the path: #path-seg#0, #path-seg#1, #path-seg#2, and so on.
For mappings found by path matching, all non-matching path segments will be interpreted as parameter values. For mappings found by regex matching, all path segments will be interpreted as parameter values.
  • Example 1
  • A request to "/auth-admin/rest/users/17/lock/" with entry path "/auth-admin/rest/" leads to the generation and verification of the following parameters:

  • #path-seg#2 = users
  • #path-seg#3 = 17
  • #path-seg#4 = lock
  • Example 2
  • The same request as in Example 1 with an entry path regex .*auth-admin.* leads to the generation and verification of the following parameters:

  • #path-seg#0 = auth-admin
  • #path-seg#1 = rest
  • #path-seg#2 = users
  • #path-seg#3 = 17
  • #path-seg#4 = lock
Treat JSON objects as parameters
If enabled, Airlock Gateway parses JSON objects in requests and filters JSON attributes with allow rules and deny rules (see JSON filtering for details).
JSON content type
JSON objects are parsed only if their content type matches the specified pattern.