0

The header is added via message inspector which implements IClientMessageInspector in method

public object BeforeSendRequest(ref Message request, IClientChannel channel)
            {
                var reqMsgProperty = new HttpRequestMessageProperty();
                reqMsgProperty.Headers.Add("SOAPAction", "SendEcho");
                reqMsgProperty.Headers.Add("Content-Type", "text/xml;charset=UTF-8");
                request.Properties[HttpRequestMessageProperty.Name] = reqMsgProperty;
                //...
                return null;
            }

But still it returns this weird message:

The SOAP action specified on the message, '"SendEcho"', does not match the action specified on the HttpRequestMessageProperty, 'SendEcho'.

Is it possible that this header should be added in some other way so it wouldn't have the double quotes surrounding it like a string? If yes then how?

Get
  • 13
  • 3

1 Answers1

0

The SOAPAction HTTP header is required for SOAP 1.1 communication, but not required for SOAP 1.2 communication.WCF follows this specification and only includes this header when using SOAP 1.1.
What binding do you use? BasicHttpBinding uses SOAP 1.1, but WSHttpBinding uses SOAP 1.2 and WS-Addressing 1.0.
You can read: SOAPAction HTTP header field specification and this thread
You also can try to define your own custom binding:
How to add a custom HTTP header to every WCF call?
Adding Http Header in an existing WCF SOAP Service is not working

Lan Huang
  • 613
  • 2
  • 5
  • Yes it is SOAP 1.1. The issue was actually the other way around, reqMsgProperty.Headers.Add("SOAPAction", "SendEcho"); was missing double qotes - with reqMsgProperty.Headers.Add("SOAPAction", "\"SendEcho\""); it went forward. This was suggested in post Thursday, June 24, 2010 9:54 PM in the second link you added. Thanks! – Get Dec 02 '21 at 10:47