Hello, I have been trying to implement the most simplest of WebService calls from Notification Services. NS hits the Webservice, but fails out with the a Request Format exception message. Does anyone know how to rewrite the content type generated by NS in the IHttpProtocolProvider The webservice generated SOAP message wants Content-Type: text/xml; charset=utf-8 However looks like NS is generating Content-Type: ;charset=utf-8 When I add the ContentType argument to Instance Config File, the value gets prepended to the NS generated contenttype which ends up looking like: text/xml;charset=utf-8 (no space after semi-colon?) which still generates the invalid format exception. Any ideas here? The exception looks like: System.InvalidOperationException: Request format is invalid: ;charset=utf-8. at System.Web.Services.Protocols.HttpServerProtocol.ReadParameters() at System.Web.Services.Protocols.WebServiceHandler.Invoke() at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest() The SOAP Message Header looks like this: - <HTTPHeaders> <content-type>;charset=utf-8</content-type> <host>localhost:8080</host> <content-length>201</content-length> <expect>100-continue</expect> <connection>Keep-Alive</connection> </HTTPHeaders> The constructed SOAP message looks like this: <?xml version="1.0" encoding="utf-8" ?> <soap:envelope> <soap:body> <Diarise xmlns='http://Blah.BlahServices.Notifications'> <DiaryID>1078</DiaryID> </Diarise> </soap:body> </soap:envelope> The Webmethod looks like this: [WebMethod] public bool Diarise(int DiaryID) { System.Diagnostics.Trace.WriteLine("Starting Diarise webmethod"); return true; }
the IHttpProtocolProvider does not generate a soap envelope so easiest to take the call to an aspx page and then reformat the request to a soap call kate
