Strip Headers Connector
Design and Implementation
Note:
- RFC does not allow stripping original HTTP header fields like Server. For more information see https://www.w3.org/TR/ct-guidelines/#sec-altering-header-values.
- In cases where Header cannot be removed, the value of the header gets masked with Mashery Proxy.
Implementation Details
- While pre-processing the request, the Connector retrieves the configured headers in preInput and searches for the configured headers within the target request. If the header is found, the Connector removes that header (key, value pair) from the target request.
- While post-processing the response, the Connector retrieves the configured headers in postInput and searches for the configured headers within the target response. If the header is found then Connector removes that header (key, value pair) from the target response.
Configuring Endpoint Processing
To configure Strip Header call processing for an endpoint:
- From the
TIBCO Cloud Mashery Control Center dashboard, navigate to
Design > API Definitions, then click the desired API definition from the list.
- Click an existing endpoint on the
Endpoints page.
- Click
Call Transformations in the left-hand menu.
- In the
Call Transformations page, specify the following information in these fields:
- Processing Adapter: Mashery_Proxy_Processor_StripHeaders
- Perform Pre-Processing: Enabled
-
Data to make available for pre-processing:
headers:<comma separated headers field>
Example:
headers:Server
- Click Save when done.
Chaining
The Strip Headers connector can be chained with other TIBCO Mashery connectors, as well as TIBCO Mashery adapters developed as processors.
For more information on chaining two processors, see Chaining Processors.