none
HTTPS Contract Mismatch issue WCF RRS feed

  • Question

  • An unhandled exception of type 'System.ServiceModel.ProtocolException' occurred in mscorlib.dll

    Additional information: The content type application/xml; charset=utf-8 of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 710 bytes of the response were: '<Fault xmlns="http://schemas.microsoft.com/ws/2005/05/envelope/none"><Code><Value>Sender</Value><Subcode><Value xmlns:a="http://schemas.microsoft.com/ws/2005/05/addressing/none">a:ActionNotSupported</Value></Subcode></Code><Reason><Text xml:lang="en-US">The message with Action '' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver.  Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).</Text></Reason></Fault>'.


    Thursday, June 22, 2017 12:51 PM

All replies

  • hello Alavudeen_A,

    The important message is The message with Action '' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher.

    There is a mismatch between the client and server.  If using a service reference then I suggest updating the service reference definition by right clicking on the service reference in the project.


    Cheers, Jeff

    Friday, June 23, 2017 1:33 AM