Re: [WebDNA] TLS 1.2 and [tcpconnect]

This WebDNA talk-list message is from

2018

It keeps the original formatting. numero = 113994
interpreted = N
texte = 1594--Apple-Mail=_270B0FF4-21C7-4CC6-94B5-9340CD1A5781Content-Transfer-Encoding: quoted-printableContent-Type: text/plain;charset=utf-8OK here is the php, just put it on your new server and instead of =calling your tcp to authnet call your new php page. All it does is reads =your post variables and sends them back out to authnet using the =protocol of the newer server. Again there is no reason you can=E2=80=99t =just do it with webdna I just wrote it in php. $value){$pstit .=3D "$key=3D$value"."&";}$pstit .=3D "this=3Dthat";# Start CURL session#$ch=3Dcurl_init("https://secure.authorize.net/gateway/transact.dll");//$ch=3Dcurl_init("http://65.175.90.231/printvars.php");curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);curl_setopt($ch, CURLOPT_HEADER, 0);curl_setopt($ch, CURLOPT_POSTFIELDS, $pstit); // set the fields to postcurl_setopt($ch, CURLOPT_RETURNTRANSFER, 1); // make sure we get the =response backcurl_setopt($ch, CURLOPT_POST, 1);$buffer =3D curl_exec($ch); // execute the postcurl_close($ch); // close our sessionprint_r($buffer);?>> On Mar 1, 2018, at 8:37 AM, Bob Minor wrote:>=20> No the older protocols cannot be completed turned off. Apples she=E2=80=99=ll script uses the older connection.=20>=20> All you need to do i>=20> Change the tcpconnect to your new servers page>=20> http://mynewserver.com/authnetpost.tpl =>=20> Create the page on the new server authnetpost.tpl>=20> On that page read the posted variables and resend them using the newer =servers tcp connect which is already updated. This is the same exact =code as you have on your old server. Only with the read variables.=20>=20> When I get to my server I will send you the PHP to do this, but you =can do it with WebDNA>=20> Robert Minor> Cybermill.com > 314-962-4024 ext 500>=20> On Mar 1, 2018, at 08:28, Jym Duane > wrote:>=20>> Robert>>=20>> I am in the process (expense) of moving a site to an updated server, =in order to have TLS1.2 to do the tcp connect.>>=20>> this sounds like after i do that i wont be able to still? is that due =to webdna?>>=20>> will be updated to latest centos and Apache to support the TLS1.2>>=20>> have not got completely there yet to try it.>>=20>> Please send script as a workaround either while transitioning or =after if needed would be greatly appreciated.>>=20>> PS- i think older protocols can be tuned off on the server?>>=20>> Jym>>=20>>=20>> On 3/1/2018 6:12 AM, Bob Minor wrote:>>> No not at all. I can send you the php script or you can do the same =thing with webdna on a newer server>>>=20>>> All I really do is read the post variables and resend them to =authnet as another tcpconnect so to speak. But this would be running on =an updated server.=20>>>=20>>> Robert Minor>>> Cybermill.com >>> 314-962-4024 ext 500>>>=20>>> On Mar 1, 2018, at 07:52, Brian Willson > wrote:>>>=20>>>> Yikes. Sounds complicated.>>>>=20>>>> Is there no way to tweak the [tcpconnect] script to accommodate TLS =1.2 and/or its ciphers? If not, that would prove a major setback here.>>>>=20>>>> Brian>>>>=20>>>> --->>>> Brian Willson>>>> www.3ip.com >>>>=20>>>>=20>>>>> On Mar 1, 2018, at 7:42 AM, Bob Minor > wrote:>>>>>=20>>>>> I got around it by running my own Linux server that does the php =call to authnet and dumps the data just as the gateway did. kinda like a =gateway for my gateway.=20>>>>>=20>>>>> Robert Minor>>>>> Cybermill.com >>>>> 314-962-4024 ext 500>>>>>=20>>>>> On Mar 1, 2018, at 06:34, Brian Willson > wrote:>>>>>=20>>>>>> Hey, everybody.>>>>>>=20>>>>>> 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.>>>>>>=20>>>>>> 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.>>>>>>=20>>>>>> (I'd mistakenly assumed all I needed to do was make sure my =server supported TLS 1.2, duh.)>>>>>>=20>>>>>> Can anyone tell me how to make sure my script forces a connection =via TLS 1.2?>>>>>>=20>>>>>> I was hoping all I=E2=80=99d need is a tweak to this line...>>>>>>=20>>>>>> [text show=3DF]response=3D[tcpconnect =host=3Dsecure2.authorize.net =&port=3D443&ssl=3DT]>>>>>>=20>>>>>> ...but simply using =E2=80=9Cssl=3DF=E2=80=9D didn=E2=80=99t =work, ha.>>>>>>=20>>>>>> Here=E2=80=99s my main connect code:>>>>>>=20>>>>>> --->>>>>>=20>>>>>> [text show=3DF]response=3D[tcpconnect host=3Dsecure2.authorize.net =&port=3D443&ssl=3DT][!]>>>>>>=20>>>>>> [/!][tcpsend]POST /gateway/transact.dll HTTP/1.0[crlf][!]>>>>>>=20>>>>>> [/!]User-Agent: e3IP[crlf][!]>>>>>>=20>>>>>> [/!]Host: secure2.authorize.net:443 =[crlf][!]>>>>>>=20>>>>>> [/!]Content-type: application/x-www-form-urlencoded[crlf][!]>>>>>>=20>>>>>> [/!]Content-length: [countchars][content][/countchars][crlf][!]>>>>>>=20>>>>>> [/!][crlf][!]>>>>>>=20>>>>>> [/!][content][crlf][!]>>>>>>=20>>>>>> [/!][/tcpsend][/tcpconnect][/text]>>>>>>=20>>>>>> --->>>>>>=20>>>>>> Thanks so much in advance for any help you can offer.>>>>>>=20>>>>>> Brian>>>>>>=20>>>>>> --->>>>>> Brian Willson>>>>>> www.3ip.com >>>>>>=20>>>>>> --------------------------------------------------------- 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 =------------------------------------------------=--------- 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 >>>> --------------------------------------------------------- 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 =------------------------------------------------=--------- 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 >> --=20>> Jym Duane - CTO - Purpose Media>> Creating Your Success Story>> Marketing : Television - Internet -Print>> Phone: (877) 443-1323>> Email: jym@purposemedia.com >> Web: www.purposemedia.com >>=20>> Oregon - www.GuideToOregon.com >> PO Box 1725, Jacksonville, OR 97530>>=20>> California - www.OrangeCounty.net >> PO Box 2025, Capistrano Beach, CA 92624=20>> --------------------------------------------------------- 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 =------------------------------------------------=--------- 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--Apple-Mail=_270B0FF4-21C7-4CC6-94B5-9340CD1A5781Content-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=utf-8OK =here is the php, just put it on your new server and instead of calling =your tcp to authnet call your new php page. All it does is reads your =post variables and sends them back out to authnet using the protocol of =the newer server. Again there is no reason you can=E2=80=99t just do it =with webdna I just wrote it in php.

<?php

$pstit=3D"";

foreach ($_POST as $key =3D> $value)

{

$pstit .=3D ="$key=3D$value"."&";

}

$pstit .=3D "this=3Dthat";

# Start CURL session

$ch=3Dcurl_init("https://secure.authorize.net/gateway/transact.dll");

<=div class=3D"">//$ch=3Dcurl_init("http://65.175.90.231/printvars.php");

curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);

curl_setopt($ch, CURLOPT_HEADER, 0);

curl_setopt($ch, CURLOPT_POSTFIELDS, $pstit); // set =the fields to post

curl_setopt($ch, =CURLOPT_RETURNTRANSFER, 1); // make sure we get the =response back

curl_setopt($ch, CURLOPT_POST, =1);

$buffer =3D =curl_exec($ch); = // execute the post

curl_close($ch); = = // close our session

print_r($buffer);

On Mar 1, 2018, at 8:37 AM, Bob =Minor <bob.minor@cybermill.com> wrote:
No the older protocols cannot be =completed turned off. Apples she=E2=80=99ll script uses the older =connection.

All =you need to do i

Change the tcpconnect to your new servers page

http://mynewserver.com/authnetpost.tpl

Create the page on the =new server authnetpost.tpl

On that page read the posted variables and resend them using =the newer servers tcp connect which is already updated. This is the same =exact code as you have on your old server. Only with the read =variables.
When I get to my server I will send you the PHP to do this, =but you can do it with WebDNA

Robert Minor
Cybermill.com
314-962-4024 ext 500

On Mar 1, 2018, at 08:28, Jym Duane <jym@purposemedia.com> wrote:
=20
Robert
I am in the process (expense) of moving a site to an updated server, in order =to have TLS1.2 to do the tcp connect.
this sounds like after i do that i wont be able to still? is that due to webdna?

will be updated to latest centos and Apache to support the TLS1.2
have =not got completely there yet to try it.
Please send script as a workaround either while transitioning or after if needed would be greatly appreciated.
PS- i think older protocols can be tuned off on the server?

Jym

On 3/1/2018 6:12 AM, Bob Minor =wrote:

No not at all. I can send you the php script or you can do the same thing with webdna on a newer server

All I really do is read the post variables and =resend them to authnet as another tcpconnect so to speak. But this would be running on an updated server.

Robert Minor

Cybermill.com

314-962-4024 ext 500

On Mar 1, 2018, at 07:52, Brian Willson <willson@3ip.com> wrote:

Yikes. Sounds complicated.

Is there no way to tweak the [tcpconnect] script to accommodate TLS 1.2 and/or its ciphers? If not, that would prove a major setback here.

Brian

---

Brian Willson

www.3ip.com

On Mar 1, 2018, at 7:42 AM, Bob =Minor <bob.minor@cybermill.com> wrote:

I got around it by running my own Linux server that does the php call to authnet and dumps the data just as the gateway did. kinda like a gateway for my gateway.

Robert Minor

Cybermill.com

314-962-4024 ext 500

On Mar 1, 2018, at 06:34, Brian Willson <willson@3ip.com> wrote:

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=99d =need is a tweak to this line...

[text show=3DF]response=3D[tcpconnect =host=3Dsecure2.authorize.net&port=3D443&ssl=3D=T]

...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=3D=T][!]

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

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

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

--------------------------------------------------------- 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/pa=ge.dna?numero=3D55 Bug Reporting: support@webdna.us
--=20Jym Duane - CTO - Purpose MediaCreating Your Success StoryMarketing : Television - Internet -PrintPhone: (877) 443-1323Email: jym@purposemedia.comWeb: www.purposemedia.comOregon - www.GuideToOregon.comPO Box 1725,  Jacksonville, OR 97530California - www.OrangeCounty.netPO Box 2025,  Capistrano Beach, CA 92624 
=20---------------------------------------------------------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
---------------------------------------------------------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

=---------------------------------------------------------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=_270B0FF4-21C7-4CC6-94B5-9340CD1A5781--. Associated Messages, from the most recent to the oldest:

Re: [WebDNA] TLS 1.2 and [tcpconnect] URGENT (Stuart Tremain 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] URGENT (Stuart Tremain 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] URGENT (Stuart Tremain 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] URGENT (Stuart Tremain 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] URGENT (Stuart Tremain 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] URGENT (Stuart Tremain 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] URGENT (Diane Blackmore 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Diane Blackmore 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Tom Duke 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Diane Blackmore 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Stuart Tremain 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Jym Duane 2018)
[WebDNA] TLS 1.2 and [tcpconnect] (Bob Knight 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Jym Duane 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Jym Duane 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Jym Duane 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (christophe.billiottet@webdna.us 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (dbrooke@euca.us 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (dbrooke@euca.us 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Robert Minor 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Jym Duane 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
[WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)

1594--Apple-Mail=_270B0FF4-21C7-4CC6-94B5-9340CD1A5781Content-Transfer-Encoding: quoted-printableContent-Type: text/plain;charset=utf-8OK here is the php, just put it on your new server and instead of =calling your tcp to authnet call your new php page. All it does is reads =your post variables and sends them back out to authnet using the =protocol of the newer server. Again there is no reason you can=E2=80=99t =just do it with webdna I just wrote it in php. $value){$pstit .=3D "$key=3D$value"."&";}$pstit .=3D "this=3Dthat";# Start CURL session#$ch=3Dcurl_init("https://secure.authorize.net/gateway/transact.dll");//$ch=3Dcurl_init("http://65.175.90.231/printvars.php");curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);curl_setopt($ch, CURLOPT_HEADER, 0);curl_setopt($ch, CURLOPT_POSTFIELDS, $pstit); // set the fields to postcurl_setopt($ch, CURLOPT_RETURNTRANSFER, 1); // make sure we get the =response backcurl_setopt($ch, CURLOPT_POST, 1);$buffer =3D curl_exec($ch); // execute the postcurl_close($ch); // close our sessionprint_r($buffer);?>> On Mar 1, 2018, at 8:37 AM, Bob Minor wrote:>=20> No the older protocols cannot be completed turned off. Apples she=E2=80=99=ll script uses the older connection.=20>=20> All you need to do i>=20> Change the tcpconnect to your new servers page>=20> http://mynewserver.com/authnetpost.tpl =>=20> Create the page on the new server authnetpost.tpl>=20> On that page read the posted variables and resend them using the newer =servers tcp connect which is already updated. This is the same exact =code as you have on your old server. Only with the read variables.=20>=20> When I get to my server I will send you the PHP to do this, but you =can do it with WebDNA>=20> Robert Minor> Cybermill.com > 314-962-4024 ext 500>=20> On Mar 1, 2018, at 08:28, Jym Duane > wrote:>=20>> Robert>>=20>> I am in the process (expense) of moving a site to an updated server, =in order to have TLS1.2 to do the tcp connect.>>=20>> this sounds like after i do that i wont be able to still? is that due =to webdna?>>=20>> will be updated to latest centos and Apache to support the TLS1.2>>=20>> have not got completely there yet to try it.>>=20>> Please send script as a workaround either while transitioning or =after if needed would be greatly appreciated.>>=20>> PS- i think older protocols can be tuned off on the server?>>=20>> Jym>>=20>>=20>> On 3/1/2018 6:12 AM, Bob Minor wrote:>>> No not at all. I can send you the php script or you can do the same =thing with webdna on a newer server>>>=20>>> All I really do is read the post variables and resend them to =authnet as another tcpconnect so to speak. But this would be running on =an updated server.=20>>>=20>>> Robert Minor>>> Cybermill.com >>> 314-962-4024 ext 500>>>=20>>> On Mar 1, 2018, at 07:52, Brian Willson > wrote:>>>=20>>>> Yikes. Sounds complicated.>>>>=20>>>> Is there no way to tweak the [tcpconnect] script to accommodate TLS =1.2 and/or its ciphers? If not, that would prove a major setback here.>>>>=20>>>> Brian>>>>=20>>>> --->>>> Brian Willson>>>> www.3ip.com >>>>=20>>>>=20>>>>> On Mar 1, 2018, at 7:42 AM, Bob Minor > wrote:>>>>>=20>>>>> I got around it by running my own Linux server that does the php =call to authnet and dumps the data just as the gateway did. kinda like a =gateway for my gateway.=20>>>>>=20>>>>> Robert Minor>>>>> Cybermill.com >>>>> 314-962-4024 ext 500>>>>>=20>>>>> On Mar 1, 2018, at 06:34, Brian Willson > wrote:>>>>>=20>>>>>> Hey, everybody.>>>>>>=20>>>>>> 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.>>>>>>=20>>>>>> 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.>>>>>>=20>>>>>> (I'd mistakenly assumed all I needed to do was make sure my =server supported TLS 1.2, duh.)>>>>>>=20>>>>>> Can anyone tell me how to make sure my script forces a connection =via TLS 1.2?>>>>>>=20>>>>>> I was hoping all I=E2=80=99d need is a tweak to this line...>>>>>>=20>>>>>> [text show=3DF]response=3D[tcpconnect =host=3Dsecure2.authorize.net =&port=3D443&ssl=3DT]>>>>>>=20>>>>>> ...but simply using =E2=80=9Cssl=3DF=E2=80=9D didn=E2=80=99t =work, ha.>>>>>>=20>>>>>> Here=E2=80=99s my main connect code:>>>>>>=20>>>>>> --->>>>>>=20>>>>>> [text show=3DF]response=3D[tcpconnect host=3Dsecure2.authorize.net =&port=3D443&ssl=3DT][!]>>>>>>=20>>>>>> [/!][tcpsend]POST /gateway/transact.dll HTTP/1.0[crlf][!]>>>>>>=20>>>>>> [/!]User-Agent: e3IP[crlf][!]>>>>>>=20>>>>>> [/!]Host: secure2.authorize.net:443 =[crlf][!]>>>>>>=20>>>>>> [/!]Content-type: application/x-www-form-urlencoded[crlf][!]>>>>>>=20>>>>>> [/!]Content-length: [countchars][content][/countchars][crlf][!]>>>>>>=20>>>>>> [/!][crlf][!]>>>>>>=20>>>>>> [/!][content][crlf][!]>>>>>>=20>>>>>> [/!][/tcpsend][/tcpconnect][/text]>>>>>>=20>>>>>> --->>>>>>=20>>>>>> Thanks so much in advance for any help you can offer.>>>>>>=20>>>>>> Brian>>>>>>=20>>>>>> --->>>>>> Brian Willson>>>>>> www.3ip.com >>>>>>=20>>>>>> --------------------------------------------------------- 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 =------------------------------------------------=--------- 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 >>>> --------------------------------------------------------- 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 =------------------------------------------------=--------- 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 >> --=20>> Jym Duane - CTO - Purpose Media>> Creating Your Success Story>> Marketing : Television - Internet -Print>> Phone: (877) 443-1323>> Email: jym@purposemedia.com >> Web: www.purposemedia.com >>=20>> Oregon - www.GuideToOregon.com >> PO Box 1725, Jacksonville, OR 97530>>=20>> California - www.OrangeCounty.net >> PO Box 2025, Capistrano Beach, CA 92624=20>> --------------------------------------------------------- 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 =------------------------------------------------=--------- 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--Apple-Mail=_270B0FF4-21C7-4CC6-94B5-9340CD1A5781Content-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=utf-8OK =here is the php, just put it on your new server and instead of calling =your tcp to authnet call your new php page. All it does is reads your =post variables and sends them back out to authnet using the protocol of =the newer server. Again there is no reason you can=E2=80=99t just do it =with webdna I just wrote it in php.