Tab – Request Actions

Header allow and deny lists are predefined in the default header lists.

• Additional allowed or denied headers can be added in the blank fields:
• Additional allowed headers
• Additional denied headers

New entries are applied in addition to the default list entries.

Request and response actions allow flexible administration of HTTP headers. Request and response headers can easily be modified based on patterns in header names or values. Airlock Gateway comes with a set of built-in default actions defined globally. Whether default actions are active or not is controlled globally. However, the activation state of default actions can be overridden on mappings.

Actions are identified by a name that must be unique. Built-in action names have the prefix (default).

• Global default actions can be configured here: Submenu – Default Actions
• For a complete list of all default request actions, see: Default request actions reference list
• For a complete list of all default response actions, see: Default response actions reference list