I am also getting the “Invalid HTTP response version:” regardless of whether I have altered my db table to reflect 443. It doesn’t appear as though anything has been changed on the Authorize.net account that I have set up, the only thing I have changed is that I upgraded to this latest version of Magento (0.6.14100) so I have to figure that something changed in the way that Magento receives the response from Authorize.net.
My authorizenet_debug table is totally empty, and like the others, the transactions are getting to Authorize.net, in the Authorized but not captured status, but the transaction dies with the Invalid HTTP response version error, and you are left wondering what the heck just happened.
Do you guy get the order number associated with the transaction ID in your authorize.net gateway?
I am not getting any info related to the order other than the payment.
Please let me know.
Thanks,
iPhony.
We are running the most current version of Magento as of yesterday and have been hitting the same error all day that started this thread almost a year ago…
“Gateway Request Error : Unable to read response, or response is empty”
We’ve made the update to our config table as suggested in the thread and we only have “Credit Cards (Authorize.net)” enabled. I’ve got 3 other large ecommerce sites that aren’t magento that run on Authorize.net and so I tried using the ID and Transaction Key from those sites that are working on this Magento site and it’s still giving the same error.
The only promising thing at this point is that according to this forum topic it seems that it is possible to make Authorize.net work with Magento. Unfortunately, we are dead in the water right now without any help.
We’ve also contacted Authorize.Net and they said that since the error is not their error that we are getting, they cannot help… The problem is, I don’t know how to get any more detailed since the error is pretty vague to begin with.
Im getting the exact same thing using 2 different sites both on godaddy shared hosting.
Getting error Undefined on newest 1.0 version when using authorized.net payment module.
Installed another website on a diffrent account using 1.1.2 and get the same error listed here on a fresh install.
Have 2 other websites running with OSCommerce using the same Authorize.net account that is accepting payments with no issue.
Can someone with all the information together allready post this issue in the bug tracker. I did a search and didnt find that anyone had posted this yet.