Soap header was not understood

Question

Remote wcf service needs a custom header 'MessageHeader' in the envelope. I'm adding this header, but processing response returns this error:

'The header 'MessageHeader' from the namespace 'http://www.ebxml.org/namespaces/messageHeader' was not understood by the recipient of this message, causing the message to not be processed. This error typically indicates that the sender of this message has enabled a communication protocol that the receiver cannot process. Please ensure that the configuration of the client's binding is consistent with the service's binding.'

In classic .net recommend change BasicHttpBinding on WsHttpBinding, but core doesn't support it. Can anybody give me some advices?

Possible duplicate of [WCF .NET Core - WsHttpBinding Configuration project.json](https://stackoverflow.com/questions/38209824/wcf-net-core-wshttpbinding-configuration-project-json) — Hintham, Dec 04 '18 at 10:00

score 0 · Answer 1 · answered Dec 11 '18 at 16:57

0

It appears to be a namespace issue. Please post your RQ + RS and identify what API you are using.

answered Dec 11 '18 at 16:57

Steve

21
1

Soap header was not understood

1 Answers1