Thanks for that useful link about SOAP ! You used the term "soap page" which is not equivalent to saying "SOAP webservice". A webservice is not a page in common parlance .
As to your answer, any .NET webservice allows GET and POST requests. If you browse to the asmx file and click any webmethod that uses parameters, you will find the supported protocols listed. It will also show you the sample request that must be sent as well as the parameters and content-type expected. For instance, HTTP Post would require a content-type of "application/x-www-form-urlencoded" (as usual). That is what you must replicate. You can use the HttpWebRequest class or (possibly, but I'm not sure) the WebClient class to send an HTTP POST request. On Jun 29, 11:16 pm, Gina_Marano <[email protected]> wrote: > I have a web service that uses the SOAP protocol and takes in an order > (XML) processes the order and returns the order id (request/response). > I want to be able to support the HTTP Post protocol. > > http://en.wikipedia.org/wiki/SOAP > > ~Gina_M~ > > On Jun 29, 10:35 am, Cerebrus <[email protected]> wrote: > > > > > I think we need MUCH more detail... for instance, what is a "SOAP > > page" ? > > > On Jun 29, 8:50 pm, Gina_Marano <[email protected]> wrote: > > > > I have a soap page. Is there a way to support HTTP Post (synchronous) > > > as well. > > > > Other question... Difference between a web server that accepts HTTP > > > Post and a REST server? > > > > I am all new to ASP.Net so please forgive me. > > > > ~Gina_M~- Hide quoted text - > > - Show quoted text -
