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?
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 brow...
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 connectio...
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...