To enable 
or disable 
a specific deny rule group, click on the round toggle button. Individual rules can be enabled/disabled only if blocking level Custom is used.
Click on the deny rule name to show/edit details of the rule. Editing one of the patterns opens the pattern editor pop-up.
Field name | Description |
|---|---|
Name | Select a unique, meaningful name for the deny rule. The name is visible on the mapping page. |
Parameter Name | Defines the query parameter name that should trigger the rule to block a request. |
Parameter Value | Defines the query parameter value that triggers the rule to block a request. If both the parameter name and the parameter value restriction are defined, then the two conditions are treated as a combined tuple: the value is only checked if the name matches. This is relevant if there is more than one parameter in a request. |
Header Name | Defines the HTTP header name that should trigger the rule to block a request. |
Header Value | Defines the HTTP header value that should trigger the rule to block a request. If both the header name and the header value restriction are defined, then the two conditions are treated as a combined tuple: the value is checked if the name matches. Airlock Gateway combines HTTP headers with the same name. For example, the headers |
Path | Defines the path that should trigger the rule to block a request. |
HTTP Method | Defines the HTTP method that should trigger the rule to block a request. |
Content-Type | Defines the content type that should trigger the rule to block a request. |