10-28-2014 01:48 PM
We have an older application that was written in classic ASP and uses the MSXML2.ServerXMLHttp object to send transactions to Authorize.Net. How can we tell if it's communicating via TLS so that the application will continue to work when Authorize.Net shuts off SSL v3? The Authorize.Net sample code for Classic ASP uses the Microsoft.XMLHTTP object, but from what I can tell they are essentially the same, but I guess the question becomes, is their sample code still valid and is there something else we should look to do to force TLS instead of SSL?
Thanks in advance,