Bug #4042

AuthorizeNet should use POST, not PUT

Details

Submitted	2005-04-03 20:03 UTC
From	fr33k at techie dot com
Status	Duplicate
Package	Payment_Process
PHP Version	4.3.10
OS	Debian/Sarge
Roadmaps	(Not assigned)

Comments

[2005-04-03 20:03 UTC] fr33k at techie dot com

Description:
------------
On a fully up to date debian/sarge install (all packages from apt-get, nothing home built), AuthorizeNet transactions woudl cause the script to eat 100% CPU until killed by max_execution_time. After 2 people spending a full day trying everything, I noticed Payment/Process/AuthorizeNet.php was calling for a PUT instead of a POST request. Changing this one item fixed the problem. I confirmed with AuthorizeNet support that POST should be used. Have submitted a bug report to CURL as I don't believe this error should have resulted in such nasty behaviour, and the problem did not occur until the curl_exec call.

Reproduce code:
---------------
A standard card authorization using authorize.net

Expected result:
----------------
A response from authorize.net

Actual result:
--------------
process (shows up as an apache thread) eats 100% CPU until killed by max_execution_time. No response is returned.