[WebDNA] Authorize.net and [tcpconnect]
This WebDNA talk-list message is from 2016
It keeps the original formatting.
numero = 112795
interpreted = N
texte = 378 Hi, folks. For several years, I've used a [tcpconnect] script I found in the = archives here to conduct online sales via Authorize.net's AIM solution. = It's still working great. However, Authorize.net will soon be using Akamai SureRoute to optimize = traffic, and they've rolled out some new secure URLs for testing. Well, = none of these new URLs work with my existing [tcpconnect] script. The = response I'm getting is (e.g.): HTTP/1.0 400 Bad Request Server: AkamaiGHost Mime-Version: 1.0 = Content-Type: text/html Content-Length: 207 Expires: Wed, 25 May 2016 = 19:13:31 GMT Date: Wed, 25 May 2016 19:13:31 GMT Connection: close This is especially odd since the URL I'm now successfully using... secure.authorize.net/gateway/transact.dll .... differs by only one character from the new Akamai one: secure2.authorize.net/gateway/transact.dll Is anyone else still using Authorize.net? And, if so, have you been able = to connect to any of the new Akamai URLs? Is it possible that a POST via = [tcpconnect] will simply not work with Authorize.net's new routing = system? If so, I might be in the market for a new online commerce solution. Thanks in advance. Brian --- Brian Willson www.3ip.com --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us .
Associated Messages, from the most recent to the oldest:
378 Hi, folks. For several years, I've used a [tcpconnect] script I found in the = archives here to conduct online sales via Authorize.net's AIM solution. = It's still working great. However, Authorize.net will soon be using Akamai SureRoute to optimize = traffic, and they've rolled out some new secure URLs for testing. Well, = none of these new URLs work with my existing [tcpconnect] script. The = response I'm getting is (e.g.): HTTP/1.0 400 Bad Request Server: AkamaiGHost Mime-Version: 1.0 = Content-Type: text/html Content-Length: 207 Expires: Wed, 25 May 2016 = 19:13:31 GMT Date: Wed, 25 May 2016 19:13:31 GMT Connection: close This is especially odd since the URL I'm now successfully using... secure.authorize.net/gateway/transact.dll .... differs by only one character from the new Akamai one: secure2.authorize.net/gateway/transact.dll Is anyone else still using Authorize.net? And, if so, have you been able = to connect to any of the new Akamai URLs? Is it possible that a POST via = [tcpconnect] will simply not work with Authorize.net's new routing = system? If so, I might be in the market for a new online commerce solution. Thanks in advance. Brian --- Brian Willson www.3ip.com --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us .
Brian Willson
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
I guess I have a problem with commitment (2003)
Stinkin' [Referrer] (1998)
Emailer setup (1997)
WC2b15 File Corruption (1997)
OUTSIDE LINKS TO SHOW SHOPPING CART????????? (1998)
Share Snippet? (1999)
Add a field to the error log? (1997)
User agent based content... (2004)
Permissions (once again) (2003)
Unauthorized User trouble (1998)
[/application] error? (1997)
WCS Newbie question (1997)
Erotic Sites (1997)
Protect (1997)
[WebDNA] Windows v7 (2011)
Weird Math and SV (1997)
PCS Customer submissions ? (1997)
[WebDNA] Open Source CMS (2012)
pop up menu's (1998)
Multiple Newcarts (1996)