I actually already had that attribute on the server. It turns out that the
problem was subtle.
The sent XML uses NS declaration as xmlns:tns="http://tempuri.org
Changing that to xmlns:tns="http://tempuri.org/"; "note the ending slash"
rectified the problem.
Regards
Vijay
>
>I am sending the
will be retired 7/1/02
><[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: [DOTNET] SOAP Problems with ASP.NET
>Date: Thu, 13 Jun 2002 11:33:19 -0700
>MIME-Version: 1.0
>Received: from hotmail.com ([65.54.236.31]) by hotmail.com with Microsoft
>SMTPSVC(5.0.2195.4905); Thu, 13
Did that too, still the same result.
Regards
Vijay
-Original Message-
From: Christian Weyer [mailto:
Sent: Thursday, June 13, 2002 11:43 AM
To: [EMAIL PROTECTED]
Subject: Re: [DOTNET] SOAP Problems with ASP.NET
Try to avoid the "" when specifying the SAOPAction HTTP heade
Try to avoid the "" when specifying the SAOPAction HTTP header.
Cheers,
Christian
-
.NET XML Web Services Repertory
http://www.xmlwebservices.cc/
-
Tewari, Vijay wrote:
> I am sending the following explicitly using sockets to
I am sending the following explicitly using sockets to a ASP.NET service
POST /HelloWorldService/Service1.asmx HTTP/1.1
Content-Type: text/xml; charset=utf-8
SOAPAction: "http://tempuri.org/Add";
Content-Length: 544
Expect: 100-continue
Connection: Keep-Alive
Host: localhost
http://schemas.xmlso
