Sorry, we are using Unidata. The SOAP requests work fine outside of HTTPS. What we are trying to do is implement a HTTPS call to submit the SOAP.
Based on previous info I have received, we are implementing the HTTPS via CallHTTP. We are able to establish the SSL connection with a valid certificate, so that is not the problem. The previous info I received showed setting the HTTP headers in the CallHTTP to SOAPAction passing the URL. I have attempted to do this, as well as passing the Namespace\SoapAction, appending this on the URL, etc, and IIS consistently gives a fault error stating it did not recognize the value of SOAPAction. When I pass just the namespace and action as I do with a standard SOAP request, it give me an HTTP.STATUS of invalid media type. Again, the XML work fine outside of the CallHTTP. Thanks, Steve Long Spyderweb Technical Services, Inc. (360) 687-8797 Washington (503) 406-8797 Oregon (866) 354-5913 Fax -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Tony Gravagno Sent: Monday, December 05, 2011 1:44 PM To: [email protected] Subject: Re: [U2] SOAP Request via an HTTPS call > From:Steve Long > I am trying to submit a SOAP request via a secure > connection, and have been unsuccessful so far. We are > able to create the secure connection, but it is > failing on the SOAP request at the IIS server with a > fault error. > > Does anyone have an example they can provide for > submitting SOAP calls in this manner? You didn't mention your DBMS, OS, or the technology being used for the SOAP client. I'm guessing you're using CallHTTP. Web Service faults are usually the result of something wrong with your XML, probably a data type issue, and often related to arrays, strongly typed complex objects, or differences in the definition of data types like Float, Decimal, Long, etc. The issues can be resolved with more careful crafting of the outbound XML. If your calling from Windows then the easiest solution is to generate a client off of the server WSDL, save the client as a ..exe, then SH to execute the new web service client. I have a video which demonstrates this on my website: remove.nospam.pleaseNebula-RnD.com/products/gallery.htm You can create this solution in just a few minutes and then you're done with it - or you can struggle for days to get CallHttp to do it for you. Take your pick. Shelling out like that isn't the most performant approach, but you're using a web service in the first place and performance can't be that great a concern. Please let us know if any of this helps. These tips can be crafted to suit various environments. HTH Tony Gravagno Nebula Research and Development TG@ remove.pleaseNebula-RnD.com Nebula R&D sells Pick/MultiValue products worldwide, and provides related development services remove.pleaseNebula-RnD.com/blog Visit PickWiki.com! Contribute! http://Twitter.com/TonyGravagno _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
