topic Re: classic asp stopped posting using Server.CreateObject("Microsoft.XMLHTTP") last night in Integration and Testing

classic asp stopped posting using Server.CreateObject("Microsoft.XMLHTTP") last night

larkhel — Wed, 20 Sep 2017 18:10:04 GMT

Hello, I have been using Classic asp and using the same posting method for awhile now. I know Authorize.net is going to disable the TLS 1.0 and we are moving the site to the new server, but since last night my site stopped posting payments.

I'm using

Dim objRequest, post_response
Set objRequest = Server.CreateObject("Microsoft.XMLHTTP")

objRequest.open "POST", post_url, false
objRequest.send post_string
post_response = objRequest.responseText
Set objRequest = nothing

I've tried

'Set objRequest = Server.CreateObject("MSXML2.ServerXMLHTTP")
'Set objRequest = Server.CreateObject("Msxml2.XMLHTTP")

as well with no luck.

The server company has not changed anything on their end. I'm at a loss on what to try. Any suggestions?

Re: classic asp stopped posting using Server.CreateObject("Microsoft.XMLHTTP") last night

Aaron — Wed, 20 Sep 2017 18:15:42 GMT

Hi @larkhel,

Can you provide any more information? Is this with requests to the sandbox or to production or both? What URL is it trying to connect to? Are you getting any error returned to your code?

Re: classic asp stopped posting using Server.CreateObject("Microsoft.XMLHTTP") last night

larkhel — Wed, 20 Sep 2017 18:48:19 GMT

It happens in the sandbox, but worked fine live prodution. (this is why i didn't want to mess with it until november)

I post to the below gateway.

post_url = "https://secure.authorize.net/gateway/transact.dll"

I don't receive any response.relay, so i'm assuming it's with the post to A.net

line 221 is objRequest.send post_string

Re: classic asp stopped posting using Server.CreateObject("Microsoft.XMLHTTP") last night

Aaron — Thu, 21 Sep 2017 15:23:57 GMT

If it doesn't work in sandbox, but does work in production, it's likely that your server is not making a TLS 1.2 connection. We turned off versions of TLS <1.2 in the sandbox back in April, and will do the same for production in February 2018.

If that's the case, you may need to apply some updates at the server level to make sure the OS installed crypto libraries properly support TLS 1.2, But, in your code, you'll likely just need to change your request to MSXML2.ServerXMLHTTP.6.0.

Re: classic asp stopped posting using Server.CreateObject("Microsoft.XMLHTTP") last night

larkhel — Wed, 20 Sep 2017 19:39:26 GMT

I will pass the message on to them.

When I change myÂ

Set objRequest = Server.CreateObject("Microsoft.XMLHTTP")

Set objRequest = Server.CreateObject("MSXML2.ServerXMLHTTP.6.0")

I recieve the following error

msxml6.dllÂ error '80090326'

The message received was unexpected or badly formatted.

Am I assuming they need to up date their version as well.

Re: classic asp stopped posting using Server.CreateObject("Microsoft.XMLHTTP") last night

Aaron — Wed, 20 Sep 2017 19:47:38 GMT

@larkhel wrote:

Am I assuming they need to up date their version as well.

That would be my guess. Keep us updated as to what they say.

Re: classic asp stopped posting using Server.CreateObject("Microsoft.XMLHTTP") last night

larkhel — Wed, 20 Sep 2017 19:49:41 GMT

will do, I sent them what you said about the crypos. I appreicate it. I know classic asp is old school, but works so well.

Re: classic asp stopped posting using Server.CreateObject("Microsoft.XMLHTTP") last night

gplough — Thu, 21 Sep 2017 14:44:51 GMT

I am having the same issue. What do you guys mean by, "Am I assuming they need to up date their version as well." Are you referring to the version of Microsoft.XML on the server?

I am running Win03 Server / IIS6

Re: classic asp stopped posting using Server.CreateObject("Microsoft.XMLHTTP") last night

Aaron — Thu, 21 Sep 2017 15:11:11 GMT

Hi @gplough,

If you're running Windows Server 2003, you won't be able to connect to us. That operating system does not support connections using TLS 1.2. You'd have to upgrade to at least 2008.

Re: classic asp stopped posting using Server.CreateObject("Microsoft.XMLHTTP") last night

gplough — Thu, 21 Sep 2017 15:21:02 GMT

Was yesterday the 20th the cutoff date for that? Because we've been connecting fine since then.

Thanks for the reply sir!

Re: classic asp stopped posting using Server.CreateObject("Microsoft.XMLHTTP") last night

larkhel — Thu, 21 Sep 2017 15:26:56 GMT

They are still working on trying to get classic asp to work on the windows iis 7.5. I need a back up plan if they can't do this.

I currently use AIM where people fill out a form and it posts to A.net.

Ok Here's what I need it to do and I'm not sure if there is a way to do this, even if I use a 3rd party company to talk between my site and authorize.net.

I need to send a custom amount, custom desc, custom number to the 3rd party useing post method like now or on A.net (simple check out will not work)

After they pay, they must come back to the site to make the order approved. I can even collect the informaiton in a custom URL code and use request.query.

Everywhere I look, I see the either the simple button method or fully intigrated. If anyone know a company that works with A.net, i'm all ears.

Re: classic asp stopped posting using Server.CreateObject("Microsoft.XMLHTTP") last night

Aaron — Thu, 21 Sep 2017 15:39:53 GMT

@gplough wrote:

Was yesterday the 20th the cutoff date for that? Because we've been connecting fine since then.

TLS 1.0 and 1.1 were disabled in sandbox back in April, but if you noticed a change recently in production, that's possibly due to disablement of the insecure 3DES cipher.

3DES was already disabled in sandbox, but was disabled in production on or shortly after September 18th.

This change had been communicated here and in several email messages to merchants over the last several months, but unfortunately still caught a few people by surprise.

Re: classic asp stopped posting using Server.CreateObject("Microsoft.XMLHTTP") last night

NexusSoftware — Thu, 21 Sep 2017 15:54:25 GMT

It shouldn't be any problem running classic ASP on Windows with IIS 7.5. We are managing many servers with the same configuration.

As an alternative you could easily post a custom amount, custom description and custom number via Ajax to our secure application and see the results of the transaction instantly on the same page or redirect to your receipt / thank you page, all without leaving your site.

Re: classic asp stopped posting using Server.CreateObject("Microsoft.XMLHTTP") last night

larkhel — Thu, 21 Sep 2017 16:56:56 GMT

How do i find out more about the secure application using Ajax?

Thank you, making me feel a little better. Thank you!!

Re: classic asp stopped posting using Server.CreateObject("Microsoft.XMLHTTP") last night

gplough — Thu, 21 Sep 2017 18:29:45 GMT

I was able to get my server working by disabling 3DES in the registry of the webserver.

https://support.microsoft.com/en-us/help/245030/how-to-restrict-the-use-of-certain-cryptographic-algorithms-and-protoc

Not that this is a solution by any means but it provided me a band-aid until the client can get the server upgraded.

Re: classic asp stopped posting using Server.CreateObject("Microsoft.XMLHTTP") last night

Aaron — Thu, 21 Sep 2017 20:08:10 GMT

Perfect! And thanks for sharing your solution here, because I'm sure that's helpful to someone else who might be in the same boat.

Re: classic asp stopped posting using Server.CreateObject("Microsoft.XMLHTTP") last night

NexusSoftware — Thu, 21 Sep 2017 20:13:29 GMT

You could contact us at https://nexwebsites.com or via a PM here with your specific requirements and we would be glad to help you achieve your objective.