topic Re: Using SIM, sandbox AuthorizeNet is timing out on redirection.. in Integration and Testing

Using SIM, sandbox AuthorizeNet is timing out on redirection..

lightwave365 — Tue, 12 Sep 2017 19:29:06 GMT

We are not sure exactly when this started happening, but whenever we try to redirect to an AuthorizeNet payment form there is a 550 error using this URL:

test.authorize.net/gateway/transact.dll

We know SIM is deprecated but as far as we know it should still be working. Does anyone know why this might be happening? We've seen this happen on multiple servers of ours.

Is the server down? If it is, how could we check the status of the server in the future?

In the header after we POST all of the information needed to that URL it will wait for about a minute and timeout with the following information in the header:

Request URL:
https://test.authorize.net/gateway/transact.dll
Request Method:
POST
Status Code:
550 Unknown
Remote Address:
104.107.43.135:443
Referrer Policy:
no-referrer-when-downgrade

If we put the wrong login information it will return instantly that there is an authentication error so the URL seems to still be working.

Re: Using SIM, sandbox AuthorizeNet is timing out on redirection..

Aaron — Wed, 13 Sep 2017 16:33:49 GMT

Hi @lightwave365,

Is this a problem you're only seeing on sandbox, or also in production?

Re: Using SIM, sandbox AuthorizeNet is timing out on redirection..

lightwave365 — Wed, 13 Sep 2017 17:15:43 GMT

We currently don't have a production account. We are trying to demo a feature for our customers using a test account.

Re: Using SIM, sandbox AuthorizeNet is timing out on redirection..

ansira_dev_2 — Wed, 13 Sep 2017 19:26:22 GMT

We are also experiencing this error in sandbox/test only.

I have not checked production directly, but given that we've continued to process orders there throughout the day, I don't think that there is an issue.

In the last test, there was pretty much an exact 90-second wait for a return (90.076, as measured by Fiddler).

I would rather not post the body of the request here, but the request header should be fine :

POST https://test.authorize.net/gateway/transact.dll HTTP/1.1
Host: test.authorize.net
Connection: keep-alive
Content-Length: 1489
Pragma: no-cache
Cache-Control: no-cache
Origin: null
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36
Content-Type: application/x-www-form-urlencoded
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.8
Cookie: UnicaNIODID=rZjHKm2zRjY-acpJVey; __utma=195058876.558140473.1502668515.1505320144.1505327112.3; __utmc=195058876; __utmz=195058876.1502668515.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); _ga=GA1.2.558140473.1502668515; _gid=GA1.2.1925465041.1505320144

Here's the response, in its entirety :

HTTP/1.1 550 Unknown
Content-Length: 0
Date: Wed, 13 Sep 2017 19:16:42 GMT
Connection: close

Re: Using SIM, sandbox AuthorizeNet is timing out on redirection..

Aaron — Wed, 13 Sep 2017 23:20:38 GMT

Hi @ansira_dev_2,

I'm still trying to duplicate on my end and haven't been able to get a failure. Is there any body in the response when you get the 550, or is the connection closed right after it sends the headers?

Re: Using SIM, sandbox AuthorizeNet is timing out on redirection..

ansira_dev_2 — Thu, 14 Sep 2017 14:45:36 GMT

There is no body. That is the response, in its entirety.

Here's the size of information requested and received, per Fiddler :

Bytes Sent: 2,311 (headers:822; body:1,489)
Bytes Received: 99 (headers:99; body:0)

I haven't checked to see if the connection is actually closed after this - I know that, per HTTP spec, the connection may be left open after a repsonse is completed. Is it actually important to see if the connection is closed?

(Edit : oops, forgot that the response asks for the connection to be closed. Regardless, I haven't checked, and I don't know if that's important.)

Re: Using SIM, sandbox AuthorizeNet is timing out on redirection..

ansira_dev_2 — Thu, 14 Sep 2017 15:25:50 GMT

The error continues to reproduce on our side. Please let me know what other information you need.

For the record, the connection does in fact close, although Chrome immediately decides to open a new connection immediately afterwards. I guess the browser's trying to outsmart us there - get a connection ready just in case. We should probably discard that bit of information.

Re: Using SIM, sandbox AuthorizeNet is timing out on redirection..

ansira_dev_2 — Thu, 14 Sep 2017 17:04:23 GMT

Just in case : what IP address does test.authorize.net resolve to for you?

Re: Using SIM, sandbox AuthorizeNet is timing out on redirection..

RichardH — Thu, 14 Sep 2017 20:14:04 GMT

Hello,

This issue was also reported to our developer support mailbox and escalated to a product support engineer. When we learn more, we'll update this thread.

I would recommend subscribing to this topic so that you'll be alerted via email if anyone from the community is able to respond with any comments. To subscribe, click Topic Options at the top of this thread and then select Subscribe. You'll then receive an email once anyone replies.

Thanks,

Richard

Re: Using SIM, sandbox AuthorizeNet is timing out on redirection..

RichardH — Fri, 15 Sep 2017 15:38:21 GMT

Hello @lightwave365 @ansira_dev_2

Our support specialist has asked that you send the HTTP headers to them at developer@authorize.net so they can do some further investigation.

Please refer to this thread in your email.

Richard

Re: Using SIM, sandbox AuthorizeNet is timing out on redirection..

ansira_dev_2 — Mon, 18 Sep 2017 14:21:29 GMT

The issue appears to be resolved.

Can we please have some details on what happened, and how we can assist you in solving the error quicker in the future?

Re: Using SIM, sandbox AuthorizeNet is timing out on redirection..

lightwave365 — Mon, 18 Sep 2017 19:59:58 GMT

Yeah, the issue is solved on our end too.

I also would like some kind of feedback as to why this even happened in the first place. It greatly impacted us at the worst time.

Re: Using SIM, sandbox AuthorizeNet is timing out on redirection..

Aaron — Tue, 19 Sep 2017 01:18:38 GMT

Hi everyone,

I don't have the specifics, but there was a release to update some security componenents that inadvertantly affected SIM. No effect had been seen in our testing previously, and I was never able to duplicate any problems on my end. However, that team rolled back the release, and the problems were resolved.

My sincere apologies for the affect on your testing and development workflows.

Re: Using SIM, sandbox AuthorizeNet is timing out on redirection..

snugzdev — Mon, 26 Aug 2019 19:49:52 GMT

I'm having this same error! Using a sandbox test account. I switched it from test to live to see if that would solve the problem but it's still taking forever to process. any help would be appreciated.