On specific systems only, when we call an Authorize.Net API method (production server only), we are getting the following failure: "The underlying connection was closed. An unexpected error occurred on a receive."
In researching the web, we have found the suggestion to set webRequest.KeepAlive to false in order to address this. We have noted that the source code for AuthorizeNet.DLL has two instances of references to webRequest.KeepAlive, and in both cases it is being set to true.
Would customizing the API DLL source code to set KeepAlive to false be a potential way of addresing this, or would doing so have negative consequences for the API's functionality in other respects? And more generally, are there any other ideas for addressing this issue?
12-19-2018 12:51 PM