2018

Hey, everybody.

For years I=E2=80=99ve been using [tcpconnect] to connec=t my online shopping carts with Authorize.net=E2=80=99s AIM solution, and it=E2=80=99s worked great, w=ith 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?

<=br class=3D"">

I was hoping all I=E2=80=99d need is a t=weak to this line...

   [text show=3DF]response=3D[t=cpconnect 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:

---

<=div class=3D"">

[text show=3DF]response=3D[tcpconnect host=3D=secure2.authorize.net&port=3D443&ssl=3DT][!]

<=div class=3D"">[/!][tcpsend]POST /gateway/transact.dll HTTP/1.0[crlf][!]

[/!]User-Agent: e3IP[=crlf][!]

[/!]Host:= secure2.authorize.n=et:443[crlf][!]

[/!]Content-type: application/x-www-form-urlencoded[crlf][!]

[/!]Content-length: [countchars=][content][/countchars][crlf][!]

<=div class=3D"">[/!][crlf][!]

[/!][content][crlf][!]

<=div class=3D"">[/!][/tcpsend][/tcpconnect][/text]