On 2 Mar 2018, at 17:43, Brian =Willson <willson@3ip.com> wrote:Wow -- thanks, Gary.This looks like a =perfect short-term solution for me. (I say =E2=80=9Cshort-term,=E2=80=9D =because it=E2=80=99s clear that MacOS will not support a LONG-term =solution -- so at my advanced age I might need to figure out how to =configure a Linux box.)It sounds like =I=E2=80=99ll just have to upgrade MacOSX from 10.11.x to 10.12, then =upgrade WebDNA from v8.2.x to v8.5.1 -- correct? Pretty sure I can =manage that.Question for the =community: Are there any =E2=80=9Cgotchas=E2=80=9D I should be aware of =when moving from 8.2 to 8.5 on a Mac? Or is it a fairly easy =process?(Apologies for not =having followed discussions here more closely, but WebDNA has proved so =stable and dependable over the years that I=E2=80=99ve rarely needed =to!)Thank you =again.BrianP.S. =46rom your =sample script, it even looks like my current one won=E2=80=99t need any =tweaking at all.--------------------------------------------------------- =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://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.usOn Mar =2, 2018, at 9:44 AM, IBS Ltd. <admin@ibsltd.nb.ca> wrote:Good =day,
I am on the digest - so - my response =if required will be 24 hours at the earliest! :)
Using the following setup - I have no issues with authorize.net - my scripts work =perfectly.
MacOSX 10.12.6
Mac =Mini
OpenSSL 0.9.8zh 14 Jan 2016
WebDNA-Mac-Server-8.5.1
Apache
The sandbox accounts have required TLS 1.2 since April of =2017.
For developers:
<https://community.developer.authorize.net/t5/The-Authorize-Net-=Developer-Blog/Request-for-Comments-API-Best-Practices/ba-p/53668><=br class=3D"">
Sample connect script:
[text]response=3D[tcpconnect host=3Dsecure2.authorize.net&port=3D443&ssl=3DT][!]
[/!][tcpsend]POST /gateway/transact.dll =HTTP/1.0[UnURL]%0D%0A[/UnURL][!]
[/!]Host: secure2.authorize.net:443[UnURL]%0D%0A[/UnURL][!]
[/!]User-Agent: StoreBuilder[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]
=E2=80=94
Gary NightingaleOn Mar 2, 2018, at 2:00 =AM, talk@webdna.us wrote:
From: Brian Willson <willson@3ip.com>
Subject: [WebDNA] TLS 1.2 and [tcpconnect]
Date: =March 1, 2018 at 8:34:06 AM AST
To: talk@webdna.us
Reply-To: <talk@webdna.us>
Hey, everybody.
For years I=E2=80=99=ve been using [tcpconnect] to connect my online shopping carts with Authorize.net=E2=80=99s =AIM solution, and it=E2=80=99s worked great, with only a minor tweak or =two required.
Yesterday, Authorize.net began requiring connections =via the TLS 1.2 protocol, and my script broke. I.e., it can no longer =connect to the endpoint.
(I'd mistakenly =assumed all I needed to do was make sure my server supported TLS 1.2, =duh.)
Can anyone tell me how to make sure =my script forces a connection via TLS 1.2?
I =was hoping all I=E2=80=99d need is a tweak to this line...
[text show=3DF]response=3D[tcpconnec=t host=3Dsecure2.authorize.net&port=3D443&ssl=3DT]
...but simply using =E2=80=9Cssl=3DF=E2=80=9D =didn=E2=80=99t work, ha.
Here=E2=80=99s my =main connect code:
---
[text show=3DF]response=3D[tcpconnect host=3Dsecure2.authorize.net&port=3D443&ssl=3DT][!]
[/!][tcpsend]POST /gateway/transact.dll =HTTP/1.0[crlf][!]
[/!]User-Agent: =e3IP[crlf][!]
[/!]Host: secure2.authorize.net:443[crlf][!]
[/!]Content-type: =application/x-www-form-urlencoded[crlf][!]
[/!]Content-length: =[countchars][content][/countchars][crlf][!]
[/!][crlf][!]
[/!][content][crlf][!]
[/!][/tcpsend][/tcpconnect][/text]
---
Thanks so much in advance =for any help you can offer.
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://www.webdna.us/page.dna?numero=3D55
Bug= Reporting: support@webdna.us
|
On 2 Mar 2018, at 17:43, Brian =Willson <willson@3ip.com> wrote:Wow -- thanks, Gary.This looks like a =perfect short-term solution for me. (I say =E2=80=9Cshort-term,=E2=80=9D =because it=E2=80=99s clear that MacOS will not support a LONG-term =solution -- so at my advanced age I might need to figure out how to =configure a Linux box.)It sounds like =I=E2=80=99ll just have to upgrade MacOSX from 10.11.x to 10.12, then =upgrade WebDNA from v8.2.x to v8.5.1 -- correct? Pretty sure I can =manage that.Question for the =community: Are there any =E2=80=9Cgotchas=E2=80=9D I should be aware of =when moving from 8.2 to 8.5 on a Mac? Or is it a fairly easy =process?(Apologies for not =having followed discussions here more closely, but WebDNA has proved so =stable and dependable over the years that I=E2=80=99ve rarely needed =to!)Thank you =again.BrianP.S. =46rom your =sample script, it even looks like my current one won=E2=80=99t need any =tweaking at all.--------------------------------------------------------- =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://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.usOn Mar =2, 2018, at 9:44 AM, IBS Ltd. <admin@ibsltd.nb.ca> wrote:Good =day,
I am on the digest - so - my response =if required will be 24 hours at the earliest! :)
Using the following setup - I have no issues with authorize.net - my scripts work =perfectly.
MacOSX 10.12.6
Mac =Mini
OpenSSL 0.9.8zh 14 Jan 2016
WebDNA-Mac-Server-8.5.1
Apache
The sandbox accounts have required TLS 1.2 since April of =2017.
For developers:
<https://community.developer.authorize.net/t5/The-Authorize-Net-=Developer-Blog/Request-for-Comments-API-Best-Practices/ba-p/53668><=br class=3D"">
Sample connect script:
[text]response=3D[tcpconnect host=3Dsecure2.authorize.net&port=3D443&ssl=3DT][!]
[/!][tcpsend]POST /gateway/transact.dll =HTTP/1.0[unurl]%0D%0A[/UnURL][!]
[/!]Host: secure2.authorize.net:443[unurl]%0D%0A[/UnURL][!]
[/!]User-Agent: StoreBuilder[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]
=E2=80=94
Gary NightingaleOn Mar 2, 2018, at 2:00 =AM, talk@webdna.us wrote:
From: Brian Willson <willson@3ip.com>
Subject: [WebDNA] TLS 1.2 and [tcpconnect]
Date: =March 1, 2018 at 8:34:06 AM AST
To: talk@webdna.us
Reply-To: <talk@webdna.us>
Hey, everybody.
For years I=E2=80=99=ve been using [tcpconnect] to connect my online shopping carts with Authorize.net=E2=80=99s =AIM solution, and it=E2=80=99s worked great, with only a minor tweak or =two required.
Yesterday, Authorize.net began requiring connections =via the TLS 1.2 protocol, and my script broke. I.e., it can no longer =connect to the endpoint.
(I'd mistakenly =assumed all I needed to do was make sure my server supported TLS 1.2, =duh.)
Can anyone tell me how to make sure =my script forces a connection via TLS 1.2?
I =was hoping all I=E2=80=99d need is a tweak to this line...
[text show=3DF]response=3D[tcpconnec=t host=3Dsecure2.authorize.net&port=3D443&ssl=3DT]
...but simply using =E2=80=9Cssl=3DF=E2=80=9D =didn=E2=80=99t work, ha.
Here=E2=80=99s my =main connect code:
---
[text show=3DF]response=3D[tcpconnect host=3Dsecure2.authorize.net&port=3D443&ssl=3DT][!]
[/!][tcpsend]POST /gateway/transact.dll =HTTP/1.0[crlf][!]
[/!]User-Agent: =e3IP[crlf][!]
[/!]Host: secure2.authorize.net:443[crlf][!]
[/!]Content-type: =application/x-www-form-urlencoded[crlf][!]
[/!]Content-length: =[countchars][content][/countchars][crlf][!]
[/!][crlf][!]
[/!][content][crlf][!]
[/!][/tcpsend][/tcpconnect][/text]
---
Thanks so much in advance =for any help you can offer.
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://www.webdna.us/page.dna?numero=3D55
Bug= Reporting: support@webdna.us
DOWNLOAD WEBDNA NOW!
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...