cancel
Showing results for 
Search instead for 
Did you mean: 

DeliveryException: invalid content type for SOAP: TEXT/HTML

Former Member
0 Kudos

My scenario is RFC -> XI -> SOAP (synchronous), but when I test this scenario, I got the error message "DeliveryException: invalid content type for SOAP: TEXT/HTML", I search the document and change it following this blog: /people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi

1. I add a MessageTransformBean module before the original one

2. I add a transform key, the value is text/html;charset=utf-8

But when I active this channel and test again, I got another message:

XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION-HTTP 400 Bad Request.

I only find one discussion about it but I still have no idea how to solve the problem. Do I need to change my mapping ? And when field should I generated in the mapping?

Accepted Solutions (0)

Answers (2)

Answers (2)

stefan_grube
Active Contributor
0 Kudos

When you have this error message, there are mainly two reasons:

1. The URL is not correct/complete -> Open this URL in your browser. Maybe you need a firewall proxy?

2. The user/password is not correct.

Regards

Stefan

Former Member
0 Kudos

Thanks, I know your concern and I think it's not the root cause. Because I found a webservice in Internet (http://www.nanonull.com/TimeService/TimeService.asmx) and I cannot call it's service. So, I think it's not due to firewall, username, password... problem

stefan_grube
Active Contributor
0 Kudos

So, no password problem. But did you apply a proxy server in the SOAP channel?

Regards

Stefan

Former Member
0 Kudos

Yes, of course. I need to configure the proxy (with authentication) to connect to http://www.nanonull.com/TimeService/TimeService.asmx

Former Member
0 Kudos

if you have need all these correctly can you check the url as pointed by stefan. compare the this adapter url with test tool url both should be same

stefan_grube
Active Contributor
0 Kudos

And of course you have also applied the correct SOAPAction.

Sorry for bothering you, but is difficult to guess the error, but in my experience, must issues are due to wrong configuration.

Could you check with TCPGateway, what error is sent back?

/people/stefan.grube/blog/2007/03/29/troubleshooting-soap-http-and-mail-adapter-scenarios-with-tcpgateway

Regards

Stefan

stefan_grube
Active Contributor
0 Kudos

> 2. I add a transform key, the value is

> text/html;charset=utf-8

In a SOAP call this value <b>must not</b> be text/html.

Always choose <b>text/xml</b>

Regards

Stefan

Former Member
0 Kudos

Sorry, it's a typo. It's text/xml.

Former Member
0 Kudos

Dennys,

can you test the WSDL without XI and see what the response your getting . your response from webserivce is not matching.

Former Member
0 Kudos

Do you mean I should use other software? I just use Oxygen XML Editor to test this webservice, it's ok. I can send and get response.

Former Member
0 Kudos

that is ok .is ur response is SOAP format.