Hi guys,

I am having a web service and client built using SoapService and SoapClient
respectively. My client needs to a custom header (derived from
System.web.services,Protocols.SoapHeader) with mustUnderstand attribute to
be true.

WSE2 doc says :
Users who want to process a mustUnderstand header should use a custom input
filter and not content-based routing. The mustUnderstand fault checking is
done before the ProcessRequestMessage method is called, so attempting to use
content-based routing will always result in a mustUnderstand fault at the
client.

So, I added custom output filter at client side to add the custom header and
custom input filter to process the custom header. My problem is how do I
tell the system that I understand the header ?.

The exception that I am getting is :

Unhandled Exception: System.Web.Services.Protocols.SoapException:
System.Web.Ser
vices.Protocols.SoapHeaderException: WSE011: The input was not a valid SOAP
mess
age because the following header was not understood: Correlation.
  at
Microsoft.Web.Services2.Messaging.SoapReceiver.ProcessMessageHeaders(SoapE
nvelope message)
  at
Microsoft.Web.Services2.Messaging.SoapReceiver.ProcessMessage(SoapEnvelope
message)
  at
Microsoft.Web.Services2.Messaging.SoapClient.SendRequestResponse(String me
thodname, SoapEnvelope envelope)
  at axalto.Test.AuthenticateServiceClient.DoAuthentication(SoapEnvelope
envelo

If somebody could throw a light on this, I will be very grateful.

Regards & thanks
Kapil Sachdeva
http://www.dotnetcard.com/blogs/ksachdeva