Andre,
I expect that you are using the @URL command to access the remote SOAP service. This tag was often used with the useragent= attribute overloaded to allow for additional header elements, such as the Content-Type header to be set. This was only ‘allowed’ to happen on older OSes, typically without IE 7 installed, although I’m not clear exactly what Microsoft update changes the behavior. In TeraScript 6.1, the new Web Call action is designed to allow for all http headers to be set directly, including the Content-Type. In fact, we’ve put a lot of effort into the Web Call action since remote services (SOAP, REST, XML, and others) are in widespread use today and TeraScript need to be a consumer of these services. TeraScript 7 and 8 will see even more improvements in this area. Because TeraScript 6.x is designed to run on the 2008 platform, I strongly recommend upgrading. You will receive a number of benefits in stability, performance, and functionality. If upgrading is not an option, then I recommend that you use the COM interface to make use of the WinHTTPRequest 5.1 object. This object does the same thing that @URL does, but will solve your issue. Your .NET programmer should be able to write for this COM object easily, as I believe the COM and .NET interface is similar. Regarding your question of WISP. The WISP protocol has not changed since version 5.5. We have purposefully maintained backwards compatibility. Therefore if your WISP software can be updated to the v5.5 WISP client, I believe that it will function against any 6.x version of the server. Robert From: Andre Rekhtine [mailto:[email protected]] Sent: Friday, February 15, 2013 4:44 PM To: [email protected] Subject: TeraScript-Talk: Outbound SSL on WISP on Windows 2008 Greetings everyone. While migrating the Witango 5.0 based web farm from Windows 2003 over to Windows 2008 R2 platform our team has faced a pesky issue. None of the migrated TAFs would NOT be able to establish a connection with the remote SOAP service. What we saw in the log files the HTTP headers ends up being stripped out from the outgoing packet. The application files were executed via WISP client for Witango 5.0, and via Browser, producing the same results on x32 Windows 2008/ x64 Windows2008R2/ x64 Windows7. The data exchange was working flawlessly on WISP and IIS6 on x32 and x64 Windows 2003 R2 platform. Our developers have successfully executed the same operations in .NET app. However it represents significant unexpected investments to re-code all data exchange processes in .NET for the client. I was wondering if anyone had similar experience with Witango5 and Windows 2008R2 As well as if there’s a WISP execution environment for the current version of Terascript? Sincerely Andre Rekhtine IT Director, M.Sc., MCSE Moveable Online Inc. +1 (416) 532-5690 [email protected] <mailto:[email protected]> _____ To unsubscribe from this list, please send an email to [email protected] <mailto:[email protected]> with "unsubscribe terascript-talk" in the body. ---------------------------------------- To unsubscribe from this list, please send an email to [email protected] with "unsubscribe terascript-talk" in the body.
