[WebDNA] TLS 1.2 and [tcpconnect]
This WebDNA talk-list message is from 2018
It keeps the original formatting.
numero = 113988
interpreted = N
texte = 1588--Apple-Mail=_C6668744-82FE-4FA9-95D8-5F19A2FDB1E7Content-Transfer-Encoding: quoted-printableContent-Type: text/plain;charset=utf-8Hey, everybody.For years I=E2=80=99ve 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[tcpconnect =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 Willsonwww.3ip.com
--Apple-Mail=_C6668744-82FE-4FA9-95D8-5F19A2FDB1E7Content-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=utf-8
Hey, everybody.
For years I=E2=80=99ve 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=99=d need is a tweak to this line...
...but simply =using =E2=80=9Cssl=3DF=E2=80=9D didn=E2=80=99t work, ha.
Here=E2=80=99s my main =connect code:
---
[/!][tcpsend]POST =/gateway/transact.dll HTTP/1.0[crlf][!]
[/!]User-Agent: e3IP[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.
=---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list talk@webdna.usTo unsubscribe, E-mail to: talk-leave@webdna.usarchives: http://www.webdna.us/page.dna?numero=3D55Bug Reporting: support@webdna.us--Apple-Mail=_C6668744-82FE-4FA9-95D8-5F19A2FDB1E7--.
Associated Messages, from the most recent to the oldest:
1588--Apple-Mail=_C6668744-82FE-4FA9-95D8-5F19A2FDB1E7Content-Transfer-Encoding: quoted-printableContent-Type: text/plain;charset=utf-8Hey, everybody.For years I=E2=80=99ve 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[tcpconnect =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 Willsonwww.3ip.com
--Apple-Mail=_C6668744-82FE-4FA9-95D8-5F19A2FDB1E7Content-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=utf-8
Hey, everybody.
For years I=E2=80=99ve 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=99=d need is a tweak to this line...
...but simply =using =E2=80=9Cssl=3DF=E2=80=9D didn=E2=80=99t work, ha.
Here=E2=80=99s my main =connect code:
---
[/!]User-Agent: e3IP[crlf]
[!]
[/!]Content-type: =application/x-www-form-urlencoded[crlf]
[!]
[/!][/tcpsend][/tcpconnect][/text]
---
Thanks so much in =advance for any help you can offer.
=---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list talk@webdna.usTo unsubscribe, E-mail to: talk-leave@webdna.usarchives: http://www.webdna.us/page.dna?numero=3D55Bug Reporting: support@webdna.us--Apple-Mail=_C6668744-82FE-4FA9-95D8-5F19A2FDB1E7--.
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:
whole word matching (2004)
Emailer Chokes on bad address (1997)
HTML Editors (1997)
[WebDNA] webdna.us Problem??? (2009)
Location of Browser Info.txt file (1997)
time and welcome (1999)
[OT] - simple JS question (2004)
Emailer (1997)
process SSI (1998)
Not really WebCat- (1997)
Random tags HELP!!!! (1999)
Time to opensource? (2006)
Hiding HTML and page breaks (1997)
Updating a database once per day - An example (1998)
Limit to Field Length in DB (1998)
AJAX with WebDNA (2006)
listfiles-looking for slick solution (1997)
Frames and WebCat (1997)
Silly Question (2003)
quantity minimum problem (1997)