topic Re: Authorize.net Service Down checker gives inconsistent results in Integration and Testing

Authorize.net Service Down checker gives inconsistent results

beeduul — Fri, 23 May 2014 20:59:36 GMT

For our site's internal status checker we are periodically requesting https://secure.authorize.net/gateway/transact.dll as recommended by Authorize.net

We check the http response code to be 200, and the body for the text "The merchant login ID or password is invalid or the account is inactive"

Yesterday we started getting a lot of errors. Some digging shows that there are two different servers responding to the above. Here are two different responses that we have gotten.

The first, a Microsoft-IIS/7.5 server, consistently displays the source of the recent errors.

$ curl -i https://secure.authorize.net/gateway/transact.dll/

HTTP/1.1 403 Forbidden

Server: Microsoft-IIS/7.5

X-Powered-By: ASP.NET

Date: Fri, 23 May 2014 19:18:17 GMT

Content-Length: 0

The second, a Microsoft-IIS/6.0 server, gives our expected and usual ping response.

$ curl -i https://secure.authorize.net/gateway/transact.dll/

HTTP/1.1 200 OK

Connection: close

Date: Fri, 23 May 2014 19:18:51 GMT

Server: Microsoft-IIS/6.0

X-Powered-By: ASP.NET

Content-Type: text/html

Content-Length: 151

Cache-Control: private, must-revalidate, max-age=0

Expires: Tue, 01 Jan 1980 00:00:00 GMT

<HTML><BODY><H3>The following errors have occurred.</H3>(13) The merchant login ID or password is invalid or the account is inactive.<BR></BODY></HTML>

Also, strangely, I was able to replicate these problems on my developer box yesterday but cannot today. However, my colleague can replicate it very easily. Our production and qa servers report sporadic errors as well. Perhaps it has something to do with the traffic shaping algorithms Authorize.net is using?

Re: Authorize.net Service Down checker gives inconsistent results

Lilith — Fri, 23 May 2014 21:29:09 GMT

$ curl -i https://secure.authorize.net/gateway/transact.dll/

Could you remove the final slash in that URL, and go to just https://secure.authorize.net/gateway/transact.dll without, please?

I can replicate with the slash, but not without.

Re: Authorize.net Service Down checker gives inconsistent results

beeduul — Sat, 24 May 2014 22:33:10 GMT

Whether it was fixed on the backendor it was a result of the URL change (although we had been using the URL with the trailing slash for a long time), the problem seems to have cleared up. Thank you!

Re: Authorize.net Service Down checker gives inconsistent results

Lilith — Tue, 27 May 2014 20:46:07 GMT

We are in the process of adding new servers to the Transact service. It's entirely possible the new servers have stricter URL policies. We did temporarily remove the new servers for the Memorial Day weekend but will be putting them back online later this week. So please be sure to leave out the final slash moving forward if you would like this automated test to work consistently.