Use the Request Transformer policy to transform a request before being passed onto the remaining API policies and finally for Pipeline execution.
Policy Execution Order
This Policy executes after authentication and authorization.
Expression Enabled Fields in API Policies
|Parameter Name||Description||Default Value||Example|
|Label||Required. The name for the API policy.||Request Transformer||ReqTrans-TestShared|
|When this policy should be applied||An expression enabled field that determines the condition to be fulfilled for the API policy to execute.||True||request.method == “POST”|
|Headers to Add/Replace|
The list of headers to add or replace into the request.
If the name or value of an entry in the table is blank, no changes are made.
|Name||The name for the header to add or replace.||N/A||X-content-type-options|
The value(s) for the header. If this field is an expression, it can return a list to simulate the header being repeated multiple times in the original request.
If the header in the original request was repeated multiple times, this new value replaces all of the original values. If the original values need to be preserved, this field should be an expression that gets the original value and returns a modified version.
|Headers to Remove||The list of headers to remove from the request. |
The subfield Name functions the same way it does for Headers to Add/Replace.
Indicates whether the API policy is enabled or disabled.
Using _ in Headers
Use '-' (dash) instead of '_' (underscore) in header name as '_' is ignored and the header is not captured. '-' is internally transformed to '_' for you to map to the Pipeline parameter. For example, HTTP-ACCEPT instead of HTTP_ACCEPT.