-
Notifications
You must be signed in to change notification settings - Fork 200
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PostData timeout #274
Comments
@dnstommy , did you ever get a resolution for this? The only solution I found would be to catch this exception and get the unsettled transactions and use the invoice number to find the transaction if it exists. |
@RickyBiggz the only thing I could do was to catch the error and throw the customer information into a queue for further review. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When submitting a payment at the line below, we are getting several timeouts per day. The timeout period is currently at 30 seconds. The customer's credit card is being charged, but since I have no response, I am not able to refund the transaction. I only have the nonce.
https://github.com/AuthorizeNet/sdk-dotnet/blob/master/Authorize.NET/Util/HttpUtility.cs#L32
19760 08:24:45 INFO Trace: Creating PostRequest Url: 'https://api2.authorize.net/xml/v1/request.api'
19760 08:24:45 INFO Trace: Retreiving Response from Url: 'https://api2.authorize.net/xml/v1/request.api'
19760 08:24:45 ERROR The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.
Exception: System.Net.WebException
Message: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.
Source: System
at System.Net.HttpWebRequest.GetResponse()
at AuthorizeNet.Util.HttpUtility.PostData[TQ,TS](Environment env, TQ request)
at AuthorizeNet.Api.Controllers.Bases.ApiOperationBase`2.Execute(Environment environment)
The text was updated successfully, but these errors were encountered: