It turned out to be a Lighttpd problem - not Authorize.net

bmoreinis's picture
Offline
Joined: 02/01/2008
Juice: 29
It turned out to be a Lighttpd problem - not Authorize.net

Hey, Ryan.

We established that it had nothing to do with Authorize.net or the secure cert, but as you said, the redirect.

I asked Kai to take a look at it, and we hard-coded the site to https:// via includes, and still, no dice...the module was somehow insisting on an http call.

Finally Kai found someone even higher on the food chain, who recommended hacking Ubercart, which he did, and which solved the problem.

I expect he'll explain the issue in more depth if/when he gets a free moment!

-Bram

NEW Authorize.net Customer Information Manager By: xerbutter (94 replies) Wed, 11/21/2007 - 12:50