We are getting below content-type mismatch error while debugging through .Net console app and making a call to soap service method using apigee proxy endpoint.Could you please let us know how to resolve this error for content type mismatch related to soap version.
Error Message:The content type application/xml of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8).
It sounds to me that the error you are showing, is an error that is emitted by the .NET Console app. Is that right? And the .NET Console app connects to a SOAP system, via an Apigee proxy. Is that right?
like this?
+--------+ +----------+ +---------+ | .NET | | Apigee | | SOAP | | client | | | | service | +--------+ +----------+ +---------+ | request | | |----------------> | | | | SOAP request | | |----------------->| | | |---+ | | | | | | |<--+ | | SOAP response | | |<---------------- | | | content-type: | | SOAP resp | ???? | |<---------------- | | | content-type: | | | application/xml | | | | | +--------+ +----------+ +---------+ | .NET | | Apigee | | SOAP | | client | | | | service | +--------+ +----------+ +---------+
If that's the case, then you need to modify the Apigee proxy to set the Content-Type header in the response, to be " application/soap+xml; charset=utf-8" . This will overwrite the existing header which has the value "application/xml" .
Does this make sense? Helpful ?
User | Count |
---|---|
5 | |
2 | |
1 | |
1 | |
1 |