I usually find this boils down to a couple of problems, the actual http headers, or the soap envelope. The xml payload is easy to test outside of udt. The headers maybe not so.
An invaluable tool is the protocolLogging databasic function, call this before and after the http call, and examine the log for the header details. Then compare this to a working example - you can treace such using curl, or some net sniffing, or a proxy like fiddler. I seem to remember that I usually manually code the entire soap payload rather than let unibasic do that as there are a number of ways of doing soap enevelopes and not all them are interoperable. - e.g. .net will not understand an Axis generated soap service as it uses structures that are not endorsed by the w3c. -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Steve Long Sent: 05 December 2011 20:53 To: U2-Users@listserver.u2ug.org Subject: [U2] SOAP Request via an HTTPS call Hi all - 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? Thanks in advance! Steve Long Spyderweb Technical Services, Inc. (360) 687-8797 Washington (503) 406-8797 Oregon (866) 354-5913 Fax _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ----- No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1411 / Virus Database: 2102/4058 - Release Date: 12/05/11 _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
