I can also state that i believe this is a new phenomena as I ran a number of SIM Auth.net test transactions (via Safari) through the site as recent as 30 days ago ...and it worked fine then. The issue seems to be something new.
I can also state that i believe this is a new phenomena as I ran a number of SIM Auth.net test transactions (via Safari) through the site as recent as 30 days ago ...and it worked fine then. The issue seems to be something new.
The way zc's Authorize.Net SIM works is the customer is taken to : https://secure.authorize.net/gateway/transact.dll after the confirmation page, fills in their details and if approved Authorize.Net grabs your HTML of checkout_success page and displays it on their website, thats why the URL is https://secure.authorize.net/gateway/transact.dll .
Up until a few weeks ago all browsers including safari displayed this "forwarded HTML" perfectly. Now however Safari's new version (5) ignores your <base> (mysite.com) html of the code and replaces it with (secure.authorize.net)'s because that is the site you are on.
So images are https://secure.authorize.net/gateway/images/product.jpg
instead of https://mysite.com/images/product.jpg
I think this is not a bug but a new security feature that apple has added. So their is no immediate solution to Safari customers, unless the zc coding is changed to work like paypal (customer is sent back to your site for success page) or all the <base> href are changed to absolute URL's on the success page.
This may seem like a small issue now, as it only affects Safari users on shops that use Authorize.Net SIM, but I think in time with more shops turning from AIM to SIM because of PCI liability and spoofing being more of an issue, most browsers will function this way.
Zencart 1.3.9h - PHP 5.2.13 - My SQL 5.0.84 - Apache 1.3.41
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donations always welcome: www.zen-cart.com/donate
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
You can try the following hack by replacing the following files with the files in the attached zip:
This is ONLY SUITABLE FOR v1.3.9d:
/includes/modules/payment/authorizenet.php
/includes/modules/checkout_process.php (no significant changes)
/includes/modules/checkout_process/header_php.php
/includes/modules/checkout_success/header_php.php
NOTE: These changes will be included in v1.3.9e
Last edited by DrByte; 15 Jul 2010 at 08:54 PM. Reason: revised with better approach
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donations always welcome: www.zen-cart.com/donate
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
I uploaded the new files:
/includes/modules/payment/authorizenet.php
/includes/modules/checkout_process.php (no changes)
/includes/modules/checkout_process/header_php.php
/includes/modules/checkout_success/header_php.php
and ran a test with Safari 5 and it works perfectly!
After the customer clicks submit on the https://secure.authorize.net/gateway/transact.dll page they are sent to a white page with centered text explaining something (loads/forwards in under a second, too fast to read) this page forwards to mysite.com's checkout_success page with CSS, images and working links!
yay!
Will this "hack" be added to the core code in the next release of 1.3.9e?
I'm a bit cautious about running custom/beta code with payment modulesesp. seeing this in the new coding:
PHP Code:MODULE_PAYMENT_AUTHORIZENET_MD5HASH == 'DANGEROUSLY-BYPASSED
Zencart 1.3.9h - PHP 5.2.13 - My SQL 5.0.84 - Apache 1.3.41
The changes will be included in v1.3.9e and newer.
The code about which you claim to be alarmed is commented-out, and therefore irrelevant.
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donations always welcome: www.zen-cart.com/donate
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
Smokin'!Thanks Dr. Byte!
![]()
Zencart 1.3.9h - PHP 5.2.13 - My SQL 5.0.84 - Apache 1.3.41
Bookmarks