Troubleshooting
Problem
When a request or response message header does not contain the Content-Type header, IBM DataPower Gateway adds "text/xml" as the Content-Type header. If the message does not match the content type, the front end client or back end server may fail to process the message as expected.
Symptom
The following is an example of this issue:
- A Multi-Protocol Gateway service is used.
- A back end server returns a html file to be displayed by a browser.
- The response message does not contain a Content-Type header.
- The Multi-Protocol Gateway Policy contains a response rule with a Results action.
- When processing the Result action, IBM WebSphere DataPower SOA Appliances injects a Content-Type with a value of "text/xml" due to the missing Content-Type header.
- The browser is unable to successfully display the html file due to the Content-Type setting of "text/xml". The source of the html file is displayed instead.
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS9H2Y","label":"IBM DataPower Gateway"},"ARM Category":[{"code":"a8m50000000CdxAAAS","label":"DataPower-\u003EDeveloper (DV)-\u003EService Config"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
08 June 2021
UID
swg21470992