updateResponseHeaderAction
Description
Update and existing response header. If the header does not exists in the original response, the header will be added.
Use {{previous}} keyword to refer to the original value of the header.
Note Headers that alter the connection behaviour will be ignored.
Evaluation scope
Evaluation scope defines the timing where this filter will be applied.
{.alert .alert-info} ::: responseHeaderReceivedFromRemote This scope occurs the moment fluxzy has done parsing the response header. :::
YAML configuration name
updateResponseHeaderAction
Settings
The following table describes the customizable properties available for this action:
{.property-table .property-table-action} ::: | Property | Type | Description | DefaultValue | | :------- | :------- | :------- | -------- | | headerName | string | | | | headerValue | string | | | | addIfMissing | boolean | | false |
:::
Example of usage
The following examples apply this action to any exchanges
Update the Server header.
rules:
- filter:
typeKind: AnyFilter
actions:
- typeKind: UpdateResponseHeaderAction
headerName: Server
headerValue: Fluxzy
.NET reference
View definition of UpdateResponseHeaderAction for .NET integration.
See also
The following actions are related to this action:
- addRequestHeaderAction
- addResponseHeaderAction
- updateRequestHeaderAction
- updateResponseHeaderAction
- deleteRequestHeaderAction
- deleteResponseHeaderAction <<<<<<< HEAD =======
- setUserAgentAction
b5d51bd2a3f1870beb9607eaba46ac93d959bb15