Offended I am not:dreamscape wrote: Didn't mean to offend you if I did, but seriously the only thing you said that I understood was "curl" and "authorize.net"
1. Yes I have fixed the curl to keep it from timing out
2. Why would I want to eliminate the call to a payment gateway in a eCommerce checkout?
3. Thanks, but I don't need any authorize.net gateway functions. I already have an Authorize.net AIM class for managing transactions that works wonderfully.
4. Authorize.net is not the problem. While technically speaking, maybe, because the script is waiting on authorize.net; however, replace authorize.net with XXX processor and the result will be the same (script waiting on XXX processor).
1. good but are you sure??...was my point it was
2. to troubleshoot the source of the problem
3. see 2 and if(2){ echo "try burritos";}
4. see 2
XMLHttp (as much as I love it), would be a poor choice in this scenario. Works with other browsers than IE it does, but SSL...sure I am not. Dependent on JS it is, and as mentioned above, cause headaches it could.
try submitting to your action page w/o the call to authorize.net you should to isolate the problem.