Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Connect-SOAP fails with Transport level information match error

SA-24477

Summary



User is on Pega 7.1.7 and reported an issue where-in while running a Connect-SOAP rule, it fails with the below error:

com.pega.pegarules.pub.services.RemoteApplicationException: SOAP service failed, error:Transport level information does not match with SOAP Message namespace URI


Error Messages



com.pega.pegarules.pub.services.RemoteApplicationException: SOAP service failed, error:Transport level information does not match with SOAP Message namespace URI


Steps to Reproduce

Invoke a Connect-SOAP rule from a data page or an activity.


Root Cause



An issue in the custom application code or rules is identified as root cause of this issue. The Content-Type for the SOAP 1.2 request HTTP header sent from Pega is set as "application/soap+xml" where-as the Content-Type for the SOAP 1.2 response HTTP header received from Service is set as "text/xml". Due to this reason there is a mismatch of Content-Type between SOAP request and response HTTP headers causing the issue.

Resolution



Ensure that Content-Type of SOAP request and SOAP response HTTP headers is matching. 

The Content-Type SOAP version 1.2 should be "application/soap+xml" and Content-Type for SOAP version 1.1 should be "application/xml" or "text/xml". 

Published June 22, 2016 - Updated October 8, 2020

Was this useful?

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us