Re: [WebDNA] Authorize.net and [tcpconnect]

This WebDNA talk-list message is from

2016

It keeps the original formatting. numero = 112808
interpreted = N
texte = 391--Apple-Mail=_A47BBD92-3AAA-44BA-BC29-45117DF674FAContent-Transfer-Encoding: quoted-printableContent-Type: text/plain;charset=windows-1252Yo, I wanted to let you folks know that the missing HOST header was in =fact the issue with my failure to connect to Authorize.net's new URLs.Adding this to my script... [/!]Host: secure2.authorize.net:443[unurl]%0D%0A[/unurl][!]....was all it took.(Why everything was working just fine @ the old URL without this header =is a mystery.)Thanks, Jym and Donovan for your help with this.Brian3IPP.S. Also changed my cryptseed, which I'd let slip into my code snippet =here, oops.> 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 =because you change one> thing on your end, doesn=92t mean they haven=92t changed requirements =on their end at the new API.>=20> HOST is often a required parameter and I don=92t 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 =code 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 "secure" (in my LIVE GATEWAY section) -- i.e., ="secure2.authorize.net" instead of "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][/m=iddle][/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 =archives here to conduct online sales via Authorize.net's AIM solution. =It's still working great.>>>>=20>>>> 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.):>>>>=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 =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?>>>>=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---Brian Willsonwww.3ip.com---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdna.us--Apple-Mail=_A47BBD92-3AAA-44BA-BC29-45117DF674FAContent-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=windows-1252Yo, I wanted to let you folks know that the missing HOST =header was in fact the issue with my failure to connect to Authorize.net's new =URLs.

Adding this to =my script...

[/!]Host: secure2.authorize.net:443[unurl]%0D%0A[/unurl][!]

...was all it =took.

(Why =everything was working just fine @ the old URL without this header is a =mystery.)

Thanks, Jym and Donovan for your help with this.

Brian

3IP

P.S. Also changed my cryptseed, which I'd let slip into my =code snippet here, oops.

On May 25, 2016, at 7:06 PM, Donovan Brooke <dbrooke@euca.us> =wrote:

Thanks, no time to look at it right now.. but just know that =just because you change one
thing on your end, doesn=92t =mean they haven=92t changed requirements on their end at the new API.

HOST is often a required parameter and I don=92t= 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]

Otherwise your best bet is to read the documentation and make =sure the code is compliant.

Donovan

On May 25, 2016, at 4:09 PM, Brian Willson <willson@3ip.com> =wrote:

On May 25, 2016, at 4:18 =PM, Donovan Brooke <dbrooke@euca.us> wrote:

Can= you post your code Brian?

Donovan

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 "secure" (in my LIVE =GATEWAY section) -- i.e., "secure2.authorize.net" instead of "secure.authorize.net."

Thanks,=
Brian

---

[!]***LIVE GATEWAY[/!]

[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]

[!]***RESPONSE[/!]

[text show=3DF]response=3D[unurl][middle =startafter=3D[url]%0D%0A%0D%0A[/url]&endbefore=3D][url][response][/url=][/middle][/unurl][/text]

[!][text =show=3DF]response=3D[grep search=3D|&replace=3D=][response][/grep][/text][/!]

[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]

On May 25, 2016, at 3:12 =PM, Brian Willson <willson@3ip.com> wrote:

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 <talk@webdna.us>.
To =unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail =to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug= Reporting: support@webdna.us

---
Brian Willson
www.3ip.com

---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail =to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug= Reporting: support@webdna.us

---

Brian Willson

www.3ip.com

=--Apple-Mail=_A47BBD92-3AAA-44BA-BC29-45117DF674FA--. Associated Messages, from the most recent to the oldest:

Re: [WebDNA] Authorize.net and [tcpconnect] ("IBS Ltd." 2016)
Re: [WebDNA] Authorize.net and [tcpconnect] (Brian Willson 2016)
Re: [WebDNA] Authorize.net and [tcpconnect] (Brian Willson 2016)
Re: [WebDNA] Authorize.net and [tcpconnect] (Brian Willson 2016)
Re: [WebDNA] Authorize.net and [tcpconnect] (Donovan Brooke 2016)
Re: [WebDNA] Authorize.net and [tcpconnect] (Brian Willson 2016)
Re: [WebDNA] Authorize.net and [tcpconnect] (Jym Duane 2016)
Re: [WebDNA] Authorize.net and [tcpconnect] (Jym Duane 2016)
Re: [WebDNA] Authorize.net and [tcpconnect] (Brian Willson 2016)
Re: [WebDNA] Authorize.net and [tcpconnect] (Brian Willson 2016)
Re: [WebDNA] Authorize.net and [tcpconnect] (Jym Duane 2016)
Re: [WebDNA] Authorize.net and [tcpconnect] (Donovan Brooke 2016)
[WebDNA] Authorize.net and [tcpconnect] (Brian Willson 2016)

391--Apple-Mail=_A47BBD92-3AAA-44BA-BC29-45117DF674FAContent-Transfer-Encoding: quoted-printableContent-Type: text/plain;charset=windows-1252Yo, I wanted to let you folks know that the missing HOST header was in =fact the issue with my failure to connect to Authorize.net's new URLs.Adding this to my script... [/!]Host: secure2.authorize.net:443[unurl]%0D%0A[/unurl][!]....was all it took.(Why everything was working just fine @ the old URL without this header =is a mystery.)Thanks, Jym and Donovan for your help with this.Brian3IPP.S. Also changed my cryptseed, which I'd let slip into my code snippet =here, oops.> 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 =because you change one> thing on your end, doesn=92t mean they haven=92t changed requirements =on their end at the new API.>=20> HOST is often a required parameter and I don=92t 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 =code 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 "secure" (in my LIVE GATEWAY section) -- i.e., ="secure2.authorize.net" instead of "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][/m=iddle][/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 =archives here to conduct online sales via Authorize.net's AIM solution. =It's still working great.>>>>=20>>>> 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.):>>>>=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 =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?>>>>=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---Brian Willsonwww.3ip.com---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdna.us--Apple-Mail=_A47BBD92-3AAA-44BA-BC29-45117DF674FAContent-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=windows-1252Yo, I wanted to let you folks know that the missing HOST =header was in fact the issue with my failure to connect to Authorize.net's new =URLs.