Some Header values do not persist to the backend
When setting header fields using the IBM WebSphere DataPower extension function dp:set-header() in a stylesheet, some or all of the headers do not show up on the back end.
Setting the DataPower variable 'var://service/routing-url' will cause the service to immediately:
- Establish a backside connection
- Send the header information
- Start streaming the body to the back end (in some cases)
A snapshot of the headers is taken and sent to the back end as soon as the DataPower variable 'var://service/routing-url' is set. Any changes or additions to headers that happen after the setting of the routing-url variable do not persist because the header values were already sent to the back end.
This behavior pertains to all methods of setting headers, including set variable actions as well as using extension elements.
More support for:
WebSphere DataPower Integration Appliance XI52
Software version: 5.0.0, 6.0.0, 6.0.1, 7.0.0
Operating system(s): Firmware
Software edition: All Editions
Reference #: 1615304
Modified date: 2013-01-18