Server found request content type to be 'text/html', but expected 'text/xml'

[Nathan]

This error came back from calling a web service.

It is a web service in nusoap php, but SOAP shoudl be able to handle
interoperability, right?

The request content type doesn't appear to be in the generated code. I'm not
sure where I have control over this or why it wouldn't be text/xml by
default.

Nathan

 

[Alex Feinman [MVP]]

This means your server has thrown an error and responded with an error page
which is html and not xml

 

[Nathan]

This means your server has thrown an error and responded with an error
page which is html and not xml

It seems to say just the opposite; that the client is sending html instead
of xml. But I believe you. I'll try to find out more of what's happening
with the server.

Nathan

 

[Alex Feinman [MVP]]

I'm sorry, I haven't been paying attention. You are right of course and my
answer makes no sense. Could you email me the server url, so that I could
take a look at the WSDL?

 

[Sergey Bogdanov]

At first, make sure that web service works correctly. It's possible that
when you make a call, the web service generates an error which was
output as HTML text.

Also make sure that content-type header was 'text/xml'. You can verify
it by using iHTTPHeaders pluggin for IE:

http://www.blunck.info/iehttpheaders.html

 

[Nathan]

I'm sorry, I haven't been paying attention. You are right of course and my
answer makes no sense. Could you email me the server url, so that I could
take a look at the WSDL?

It's a private url I couldn't post. But the problem was on the server.

It did appear that a php file was producing textual output before the
headers were sent, so the headers may have defaulted to text/html.

So even though this seems backwards from the error message, it does appear
that it was the server returning html unexpectedly.

That server side code can be a real pain to debug.

Nathan