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.
HTTP/1.1 403 Forbidden
Server: Microsoft-IIS/7.5
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.
HTTP/1.1 200 OK
Connection: close
Date: Fri, 23 May 2014 19:18:51 GMT
Server: Microsoft-IIS/6.0
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?
