Update Authorize.net to new Akamai URL.
authorLaryn <laryn@cedc.org>
Tue, 28 Jul 2015 14:47:20 +0000 (10:47 -0400)
committerLaryn <laryn@cedc.org>
Tue, 28 Jul 2015 14:47:20 +0000 (10:47 -0400)
templates/CRM/Admin/Form/Setting/Url.hlp

index e0fa910108553285c58031bb661ee8f9e0dd0961..10bfbd8771be79f99a046eaeab6224e0cb4a5ce1 100644 (file)
@@ -37,7 +37,7 @@
 {/htxt}
 {htxt id='id-verify_ssl'}
 <p>{ts}This setting will verify the SSL certificates received when making secure HTTPS connections to payment processors.{/ts}</p>
-<p>{ts}For example, in order to process a payment through Authorize.net, CiviCRM must make a request to https://secure.authorize.net/gateway/transact.dll. Using https to connect to secure.authorize.net insures that the connection is encrypted, but it's possible that CiviCRM is actually connecting to an attacker and the attacker is connecting to secure.authorize.net.{/ts}</p>
+<p>{ts}For example, in order to process a payment through Authorize.net, CiviCRM must make a request to https://secure2.authorize.net/gateway/transact.dll. Using https to connect to secure2.authorize.net insures that the connection is encrypted, but it's possible that CiviCRM is actually connecting to an attacker and the attacker is connecting to secure2.authorize.net.{/ts}</p>
 <p>{ts}Verifying the SSL certificate helps confirm that CiviCRM is securely communicating directly to payment processors.{/ts}</p>
 {/htxt}