A browser cannot call a web service normally. The content type of the post must be set to an appropriate value, which is not controllable from most browsers.
The difference is only in error reporting. Both are indicative of failures. A SOAP RPC service expects to be given a SOAP document. Armed with just a browser, this isn’t possible.
That would indicate things are set up correctly.
Three possibilities come to mind: 1) they too are using a browser to hit the URL, which is not valid; 2) they are not passing a SOAP document in their HTTP POST or are not setting the content-type to text/xml; 3) SOAP RPC has interoperability issues, which have been covered many times in the forums. Perhaps they are encountering one of these.
#soa#API-Management#webMethods