Legacy software sending XML to your web service and because it's not sending the SOAPAction header it's receiving an error from the server?
Add this attribute to your web service: [System.Web.Services.Protocols.SoapDocumentService( RoutingStyle=SoapServiceRoutingStyle.RequestElement )] This imposes a few restrictions on your web service, but allows your webservice to route via the first element in the soap:Body instead of relying on the SOAPAction header. This imposes a few restrictions on your web service, but it's not likely you'll run into them unless you change the ParameterStyle to Bare with a SoapDocumentMethodAttribute on each method. Adam.. -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Mark Fruhling Sent: Thursday, August 14, 2008 12:20 PM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: [ADVANCED-DOTNET] Problem with SOAPAction HTTP Header I'm dealing with a piece of legacy software that does automated HTTP Posts for Customer Integrations. I've looked through the source code and found that it has no mechanism for adding the "SOAPAction" Http Header. I was wondering if anyone knows if this Header can somehow be passed through the URL instead. =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
