Update to Akamai transaction URLs

Please test and let me know if this works.

I used the patch from #2557453-3: Authorize.net changes, do I need to do anything? for Ubercart 6.x and tested it on a live site and all transactions are coming through. That patch should really be on this issue even though it is for 6.x, but just wanted to note it as a +1 for RTBC for Ubercart 6.x.

This patch updates both the API URLs used by the module. The patch in #1 updates one of them.

Just received an email stating:

Using Akamai is currently optional, but will be mandatory for all merchants on June 30th 2016. Upgrade your website or payment solution today to take immediate advantage of Akamai’s benefits.

How important is this issue to move forward? Is it something that will warrant a stable release of UC or should we just go with the patch and expect it to be in the next stable?

@philsward: Have you tested the patch in #4? If so please mark this issue RTBC and it can be committed; then we should consider rolling a new release before the end of June.

My reading is that the new URLs allow sites to test and use Akamai during "phase one", then when "phase two" comes about the old URLs will switch over to using Akamai. So this patch gives you a chance to preview what it will be like after the change, and this patch should be tested by you if you are using Authorize.net to assure you that your site will continue to work after the June switchover. However, when the transition to Akamai is completed the patch will no longer be needed.

@longwave have not tested. The intention is there, just haven't gotten around to it. (Only learned of the forced switch yesterday 4/30)

@TR Based on what you mentioned, it sounds like the existing URLs are going to be redirected meaning we don't need to worry about downtime if the URLs aren't specifically coded? If so, a stable wouldn't necessarily be warranted.

I'm cool with testing to push the issue forward as committed, just trying to figure out if it's something I need to loose sleep over in the coming weeks ;-)

@TR your comment also makes me wonder if we need to worry about it at all... If the existing URLs use the new CDN after the forced switch, is there any need to commit this? It seems the testing URLs won't even be necessary.

After reading up on this a bit more, I agree there is nothing we need to do here.

https://www.authorize.net/support/akamaifaqs/#when

We will automatically direct all of our existing transaction processing URLs to connect through Akamai starting June 30, 2016. After this change, all transaction URLs will connect to Authorize.Net through Akamai.
[...]
Everything else in the API calls remains the same, and you should use the same API Login ID and Transaction Key you use today.

Anyone who wants to start using the Akamai network now can apply the patch in #4, but it is not required, and as of June 30 everyone will automatically switch to Akamai anyway.

Thanks @longwave

Sometimes issues like these just need a bit of proper clarification. It's always scary when external sources make changes because those of us who aren't as smart on that front, aren't sure what's going on or how it will affect our sites.

I speak for myself but possibly others when I say "I have enough on my plate to have to deal with something external interrupting my workflow."