App Connect

 View Only

 Strip http header

madhu ram's profile image
madhu ram posted Tue July 15, 2025 11:31 PM

Hello All,

There is a message flow here we have a soap request node to hit a webservice and get a response from it.While getting the SOAP response we receive http headers like below attached to the SOAP response.

HTTP/1.1 200 OK
Content-Type: text/xml
Server: IBM App Connect Enterprise
X-Ratelimit-Remaining
X-Ratelimit-Reset
Set-Cookie 
As a result of which we get the error


Catalog>BIPmsgs</Catalog>
                    <Severity>3</Severity>
                    <Number>3614</Number>
                    <Text>problem creating SOAP tree from bitstream</Text>


I understand the error is due to the soap:Envelope not being the root and the flow is unable to parse it .
My question is how to remove to http header  from the soap response 


Is it advisable to use the any node to clear http headers ?

My existing flow is as below :
queue->java compute->soap request->SOAPchecking logic(error and failure go to )->error handler
I don't want to touch the soap checking logic as its a common one and used by other apps too

Pleas help

Thanks 
Madhu

Brian S Paskin's profile image
Brian S Paskin posted Wed July 16, 2025 07:52 AM

The error indicates that the WSDL and message are not aligned correctly; There is a difference.  Are you sure you are sending back a proper SOAP message that confirms to the WSDL?

Brian

Kim Meynendonckx's profile image
Kim Meynendonckx IBM Champion posted Thu July 17, 2025 01:48 AM

Hi,

This error means that the response isn't a correct SOAP response. Like @Brian S Paskin says, first check if the response is a correct soap message. If you are using a wsdl the response should also match the response definition in the wsdl. If the soap-request node is set with operation mode gateway then it just needs to be a correct soap response message.

The http headers should be in http response headers logical tree and shouldn't impact the soap parsing. Once the response is parsed I don't see any issue to remove the response headers from the logical tree.

hope this helps

Kim

madhu ram's profile image
madhu ram posted Thu July 17, 2025 04:01 AM

Hello @Kim Meynendonckx , 
Thanks a lot.
Please find my response below

  1. The   WebserviceUrl for the soap request   is automatically derived from the <soap:address> element of the selected Service port from the wsdl .This was happening before introducing api gateway . The <soap:address> in wsdl was overriden by the WebService URL in soap request node and it was fine
  2. After introducing the api gateway,we have the api gateway url in the Web Service URL property of the soap request node,due to which the response could not  be parsed.
  3. But the gateway api has been configured to point to the correct url.
    Wondering if  the flow will have the Webservice url ( end application url)to be the gateway url in its response too ?

    Hope I am not confusing here .    Thanks
Kim Meynendonckx's profile image
Kim Meynendonckx IBM Champion posted Fri July 18, 2025 05:16 AM

Madhu,

I think it's usefull to test the api gateway endpoint with a tool like soapUI. Try to recreate the error with soapUI or something similar. This way you can easily validate the response you get from the apigateway.

If that is correct .. Recreate the error in your app connect development environment, debug and trace it.

If you want you can share the response from soapui so that we can have a look.

mvg

Kim

Related Content