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:
- Tab – Request Actions
- Tab – Response Actions
Actions are identified by a name that must be unique. Built-in action names have the prefix (default).
- For a complete reference of all default actions, see:
- Default Request Actions
- Default Response Actions