Re: [WebDNA] Authorize.net and [tcpconnect]
This WebDNA talk-list message is from 2016
It keeps the original formatting.
numero = 112809
interpreted = N
texte = 392 I can also confirm that adding that one header solved my issue too. So -> I thank you as well! :) WebDNA for life! -- Gary On 05/27/16 2:48 PM, "Brian Willson"
wrote: > Yo, I wanted to let you folks know that the missing HOST header was in fa= ct > the issue with my failure to connect to Authorize.net's new URLs. >=20 > Adding this to my script... >=20 > [/!]Host: secure2.authorize.net:443[unurl]%0D%0A[/unurl][!] >=20 > ...was all it took. >=20 > (Why everything was working just fine @ the old URL without this header i= s a > mystery.) >=20 > Thanks, Jym and Donovan for your help with this. >=20 > Brian > 3IP >=20 > P.S. Also changed my cryptseed, which I'd let slip into my code snippet h= ere, > oops. >=20 >=20 >> On May 25, 2016, at 7:06 PM, Donovan Brooke wrote: >>=20 >> Thanks, no time to look at it right now.. but just know that just becaus= e you >> change one >> thing on your end, doesn=B9t mean they haven=B9t changed requirements on the= ir >> end at the new API. >>=20 >> HOST is often a required parameter and I don=B9t see that in your code: >>> [text show=3DF]response=3D[tcpconnect >>> host=3Dsecure.authorize.net&port=3D443&ssl=3DT][!] >>> [/!][tcpsend]POST /gateway/transact.dll HTTP/1.0[unurl]%0D%0A[/unurl][!= ] >>> [/!]User-Agent: e3IP[unurl]%0D%0A[/unurl][!] >>> [/!]Content-type: application/x-www-form-urlencoded[unurl]%0D%0A[/unurl= ][!] >>> [/!]Content-length: >>> [countchars][content][/countchars][unurl]%0D%0A[/unurl][!] >>> [/!][unurl]%0D%0A[/unurl][!] >>> [/!][content][unurl]%0D%0A[/unurl][!] >>> [/!][/tcpsend][/tcpconnect][/text] >>=20 >>=20 >>=20 >> Otherwise your best bet is to read the documentation and make sure the c= ode >> is compliant.=20 >>=20 >> Donovan >>=20 >>=20 >>=20 >>=20 >>=20 >> On May 25, 2016, at 4:09 PM, Brian Willson wrote: >>=20 >>>> On May 25, 2016, at 4:18 PM, Donovan Brooke wrote: >>>>=20 >>>> Can you post your code Brian? >>>>=20 >>>> Donovan >>>=20 >>>=20 >>> Sure thing. Below is the code I've been using successfully for several >>> years. The new Akamai URL only differs in that it has a "2" after "secu= re" >>> (in my LIVE GATEWAY section) -- i.e., "secure2.authorize.net" instead o= f >>> "secure.authorize.net." >>>=20 >>> Thanks,=20 >>> Brian >>>=20 >>> --- >>>=20 >>> [!]***LIVE GATEWAY[/!] >>>=20 >>> [text show=3DF]response=3D[tcpconnect >>> host=3Dsecure.authorize.net&port=3D443&ssl=3DT][!] >>> [/!][tcpsend]POST /gateway/transact.dll HTTP/1.0[unurl]%0D%0A[/unurl][!= ] >>> [/!]User-Agent: e3IP[unurl]%0D%0A[/unurl][!] >>> [/!]Content-type: application/x-www-form-urlencoded[unurl]%0D%0A[/unurl= ][!] >>> [/!]Content-length: >>> [countchars][content][/countchars][unurl]%0D%0A[/unurl][!] >>> [/!][unurl]%0D%0A[/unurl][!] >>> [/!][content][unurl]%0D%0A[/unurl][!] >>> [/!][/tcpsend][/tcpconnect][/text] >>>=20 >>>=20 >>> [!]***RESPONSE[/!] >>>=20 >>> [text show=3DF]response=3D[unurl][middle >>> startafter=3D[url]%0D%0A%0D%0A[/url]&endbefore=3D][url][response][/url][/mi= ddle] >>> [/unurl][/text] >>>=20 >>> [!][text show=3DF]response=3D[grep >>> search=3D|&replace=3D ][response][/grep][/text][/!] >>>=20 >>> [listwords words=3D[response]&delimiters=3D|][!] >>> [/!][showif [index]=3D1][text show=3DF]o_status=3D[showif >>> [word]=3D1]Approved[/showif][showif [word]=3D2]Declined[/showif][showif >>> [word]=3D3]Error[/showif][/text][/showif][!] >>> [/!][showif [index]=3D4][text show=3DF]o_reason=3D[word][/text][/showif][!] >>> [/!][showif [index]=3D5][text show=3DF]o_authcode=3D[word][/text][/showif][!] >>> [/!][showif [index]=3D6][text show=3DF]o_avscode=3D[word][/text][/showif][!] >>> [/!][showif [index]=3D7][text show=3DF]o_transid=3D[word][/text][/showif][!] >>> [/!][showif [index]=3D38][text >>> show=3DF]o_hash=3D[response_1][word][/text][/showif][!] >>> [/!][/listwords] >>>=20 >>>=20 >>>> On May 25, 2016, at 3:12 PM, Brian Willson wrote: >>>>=20 >>>>> Hi, folks. >>>>>=20 >>>>> For several years, I've used a [tcpconnect] script I found in the arc= hives >>>>> here to conduct online sales via Authorize.net's AIM solution. It's s= till >>>>> working great. >>>>>=20 >>>>> However, Authorize.net will soon be using Akamai SureRoute to optimiz= e >>>>> traffic, and they've rolled out some new secure URLs for testing. Wel= l, >>>>> none of these new URLs work with my existing [tcpconnect] script. The >>>>> response I'm getting is (e.g.): >>>>>=20 >>>>> 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 >>>>>=20 >>>>> This is especially odd since the URL I'm now successfully using... >>>>>=20 >>>>> secure.authorize.net/gateway/transact.dll >>>>>=20 >>>>> ... differs by only one character from the new Akamai one: >>>>>=20 >>>>> secure2.authorize.net/gateway/transact.dll >>>>>=20 >>>>> Is anyone else still using Authorize.net? And, if so, have you been a= ble >>>>> 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 sy= stem? >>>>>=20 >>>>> If so, I might be in the market for a new online commerce solution. >>>>>=20 >>>>> Thanks in advance. >>>>>=20 >>>>> Brian >>>>>=20 >>>>> --- >>>>> Brian Willson >>>>> www.3ip.com >>>>>=20 >>>>> --------------------------------------------------------- >>>>> 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 >>>>=20 >>>> --------------------------------------------------------- >>>> 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 >>>=20 >>>=20 >>> --- >>> Brian Willson >>> www.3ip.com >>=20 >> --------------------------------------------------------- >> 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 >=20 > --- > Brian Willson > www.3ip.com >=20 --------------------------------------------------------- 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:
392 I can also confirm that adding that one header solved my issue too. So -> I thank you as well! :) WebDNA for life! -- Gary On 05/27/16 2:48 PM, "Brian Willson" wrote: > Yo, I wanted to let you folks know that the missing HOST header was in fa= ct > the issue with my failure to connect to Authorize.net's new URLs. >=20 > Adding this to my script... >=20 > [/!]Host: secure2.authorize.net:443[unurl]%0D%0A[/unurl][!] >=20 > ...was all it took. >=20 > (Why everything was working just fine @ the old URL without this header i= s a > mystery.) >=20 > Thanks, Jym and Donovan for your help with this. >=20 > Brian > 3IP >=20 > P.S. Also changed my cryptseed, which I'd let slip into my code snippet h= ere, > oops. >=20 >=20 >> On May 25, 2016, at 7:06 PM, Donovan Brooke wrote: >>=20 >> Thanks, no time to look at it right now.. but just know that just becaus= e you >> change one >> thing on your end, doesn=B9t mean they haven=B9t changed requirements on the= ir >> end at the new API. >>=20 >> HOST is often a required parameter and I don=B9t see that in your code: >>> [text show=3DF]response=3D[tcpconnect >>> host=3Dsecure.authorize.net&port=3D443&ssl=3DT][!] >>> [/!][tcpsend]POST /gateway/transact.dll HTTP/1.0[unurl]%0D%0A[/unurl][!= ] >>> [/!]User-Agent: e3IP[unurl]%0D%0A[/unurl][!] >>> [/!]Content-type: application/x-www-form-urlencoded[unurl]%0D%0A[/unurl= ][!] >>> [/!]Content-length: >>> [countchars][content][/countchars][unurl]%0D%0A[/unurl][!] >>> [/!][unurl]%0D%0A[/unurl][!] >>> [/!][content][unurl]%0D%0A[/unurl][!] >>> [/!][/tcpsend][/tcpconnect][/text] >>=20 >>=20 >>=20 >> Otherwise your best bet is to read the documentation and make sure the c= ode >> is compliant.=20 >>=20 >> Donovan >>=20 >>=20 >>=20 >>=20 >>=20 >> On May 25, 2016, at 4:09 PM, Brian Willson wrote: >>=20 >>>> On May 25, 2016, at 4:18 PM, Donovan Brooke wrote: >>>>=20 >>>> Can you post your code Brian? >>>>=20 >>>> Donovan >>>=20 >>>=20 >>> Sure thing. Below is the code I've been using successfully for several >>> years. The new Akamai URL only differs in that it has a "2" after "secu= re" >>> (in my LIVE GATEWAY section) -- i.e., "secure2.authorize.net" instead o= f >>> "secure.authorize.net." >>>=20 >>> Thanks,=20 >>> Brian >>>=20 >>> --- >>>=20 >>> [!]***LIVE GATEWAY[/!] >>>=20 >>> [text show=3DF]response=3D[tcpconnect >>> host=3Dsecure.authorize.net&port=3D443&ssl=3DT][!] >>> [/!][tcpsend]POST /gateway/transact.dll HTTP/1.0[unurl]%0D%0A[/unurl][!= ] >>> [/!]User-Agent: e3IP[unurl]%0D%0A[/unurl][!] >>> [/!]Content-type: application/x-www-form-urlencoded[unurl]%0D%0A[/unurl= ][!] >>> [/!]Content-length: >>> [countchars][content][/countchars][unurl]%0D%0A[/unurl][!] >>> [/!][unurl]%0D%0A[/unurl][!] >>> [/!][content][unurl]%0D%0A[/unurl][!] >>> [/!][/tcpsend][/tcpconnect][/text] >>>=20 >>>=20 >>> [!]***RESPONSE[/!] >>>=20 >>> [text show=3DF]response=3D[unurl][middle >>> startafter=3D[url]%0D%0A%0D%0A[/url]&endbefore=3D][url][response][/url][/mi= ddle] >>> [/unurl][/text] >>>=20 >>> [!][text show=3DF]response=3D[grep >>> search=3D|&replace=3D ][response][/grep][/text][/!] >>>=20 >>> [listwords words=3D[response]&delimiters=3D|][!] >>> [/!][showif [index]=3D1][text show=3DF]o_status=3D[showif >>> [word]=3D1]Approved[/showif][showif [word]=3D2]Declined[/showif][showif >>> [word]=3D3]Error[/showif][/text][/showif][!] >>> [/!][showif [index]=3D4][text show=3DF]o_reason=3D[word][/text][/showif][!] >>> [/!][showif [index]=3D5][text show=3DF]o_authcode=3D[word][/text][/showif][!] >>> [/!][showif [index]=3D6][text show=3DF]o_avscode=3D[word][/text][/showif][!] >>> [/!][showif [index]=3D7][text show=3DF]o_transid=3D[word][/text][/showif][!] >>> [/!][showif [index]=3D38][text >>> show=3DF]o_hash=3D[response_1][word][/text][/showif][!] >>> [/!][/listwords] >>>=20 >>>=20 >>>> On May 25, 2016, at 3:12 PM, Brian Willson wrote: >>>>=20 >>>>> Hi, folks. >>>>>=20 >>>>> For several years, I've used a [tcpconnect] script I found in the arc= hives >>>>> here to conduct online sales via Authorize.net's AIM solution. It's s= till >>>>> working great. >>>>>=20 >>>>> However, Authorize.net will soon be using Akamai SureRoute to optimiz= e >>>>> traffic, and they've rolled out some new secure URLs for testing. Wel= l, >>>>> none of these new URLs work with my existing [tcpconnect] script. The >>>>> response I'm getting is (e.g.): >>>>>=20 >>>>> 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 >>>>>=20 >>>>> This is especially odd since the URL I'm now successfully using... >>>>>=20 >>>>> secure.authorize.net/gateway/transact.dll >>>>>=20 >>>>> ... differs by only one character from the new Akamai one: >>>>>=20 >>>>> secure2.authorize.net/gateway/transact.dll >>>>>=20 >>>>> Is anyone else still using Authorize.net? And, if so, have you been a= ble >>>>> 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 sy= stem? >>>>>=20 >>>>> If so, I might be in the market for a new online commerce solution. >>>>>=20 >>>>> Thanks in advance. >>>>>=20 >>>>> Brian >>>>>=20 >>>>> --- >>>>> Brian Willson >>>>> www.3ip.com >>>>>=20 >>>>> --------------------------------------------------------- >>>>> 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 >>>>=20 >>>> --------------------------------------------------------- >>>> 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 >>>=20 >>>=20 >>> --- >>> Brian Willson >>> www.3ip.com >>=20 >> --------------------------------------------------------- >> 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 >=20 > --- > Brian Willson > www.3ip.com >=20 --------------------------------------------------------- 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 .
"IBS Ltd."
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:
Getting Crazy (1998)
WebCat2b13MacPlugIn - [showif][search][/showif] (1997)
Feature req. (2002)
WebCat2 - Getting to the browser's username/password data (1997)
I try hard to think positively (1998)
[isfile] ? (1997)
Hard Questions ? (1997)
WebCatalog for Postcards ? (1997)
Extended [ConvertChars] (1997)
Fun with dates (1997)
email stoped (2003)
Urgent WebCatalog problem (2000)
Running 2 two WebCatalog.acgi's (1996)
2.0Beta Command Ref (can't find this instruction) (1997)
Answer: WebDelivery downloads alias, not original ? (1997)
WebCommerce: Folder organization ? (1997)
WebCat2.0 acgi vs plugin (1997)
Date Formats (1997)
Version 2.0 and 1.6 simultaneous (1997)
greater than or equal to (1997)