Re: [WebDNA] TLS 1.2 and [tcpconnect]

This WebDNA talk-list message is from

2018


It keeps the original formatting.
numero = 113992
interpreted = N
texte = 1592 This is a multi-part message in MIME format. --------------D94955073D44895F140DB2A4 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Robert I am in the process (expense) of moving a site=C2=A0 to an updated server= , in=20 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=20 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=20 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=20 > thing with webdna on a newer server > > All I really do is read the post variables and resend them to authnet=20 > as another tcpconnect so to speak. But this would be running on an=20 > updated server. > > Robert Minor > Cybermill.com > 314-962-4024 ext 500 > > On Mar 1, 2018, at 07:52, Brian Willson > wrote: > >> Yikes. Sounds complicated. >> >> Is there no way to tweak the [tcpconnect] script to accommodate TLS=20 >> 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 >> > wrote: >>> >>> I got around it by running my own Linux server that does the php=20 >>> call to authnet and dumps the data just as the gateway did. kinda=20 >>> like a gateway for my gateway. >>> >>> Robert Minor >>> Cybermill.com >>> 314-962-4024 ext 500 >>> >>> On Mar 1, 2018, at 06:34, Brian Willson >> > wrote: >>> >>>> Hey, everybody. >>>> >>>> For years I=E2=80=99ve been using [tcpconnect] to connect my online=20 >>>> shopping carts with Authorize.net =E2=80=99s = AIM=20 >>>> solution, and it=E2=80=99s worked great, with only a minor tweak or = two=20 >>>> required. >>>> >>>> Yesterday, Authorize.net =C2=A0began requirin= g=20 >>>> connections via the TLS 1.2 protocol, and my script broke. I.e., it=20 >>>> can no longer connect to the endpoint. >>>> >>>> (I'd mistakenly assumed all I needed to do was make sure my server=20 >>>> supported TLS 1.2, duh.) >>>> >>>> Can anyone tell me how to make sure my script forces a connection=20 >>>> via TLS 1.2? >>>> >>>> I was hoping all I=E2=80=99d need is a tweak to this line... >>>> >>>> =C2=A0 =C2=A0[text show=3DF]response=3D[tcpconnect host=3Dsecure2.au= thorize.net=20 >>>> &port=3D443&ssl=3DT] >>>> >>>> ...but simply using =E2=80=9Cssl=3DF=E2=80=9D didn=E2=80=99t work, h= a. >>>> >>>> Here=E2=80=99s my main connect code: >>>> >>>> --- >>>> >>>> [text show=3DF]response=3D[tcpconnect host=3Dsecure2.authorize.net=20 >>>> &port=3D443&ssl=3DT][!] >>>> >>>> [/!][tcpsend]POST /gateway/transact.dll HTTP/1.0[crlf][!] >>>> >>>> [/!]User-Agent: e3IP[crlf][!] >>>> >>>> [/!]Host: secure2.authorize.net:443=20 >>>> [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=20 >>>> message is sent to you because you are subscribed to the mailing=20 >>>> list talk@webdna.us To unsubscribe, E-mail=20 >>>> to: talk-leave@webdna.us archives:=20 >>>> http://www.webdna.us/page.dna?numero=3D55 Bug Reporting:=20 >>>> support@webdna.us >>> --------------------------------------------------------- This=20 >>> message is sent to you because you are subscribed to the mailing=20 >>> list talk@webdna.us To unsubscribe, E-mail=20 >>> to: talk-leave@webdna.us archives:=20 >>> http://www.webdna.us/page.dna?numero=3D55 Bug Reporting:=20 >>> support@webdna.us >> >> --------------------------------------------------------- This=20 >> message is sent to you because you are subscribed to the mailing list=20 >> talk@webdna.us To unsubscribe, E-mail to:=20 >> talk-leave@webdna.us archives:=20 >> http://www.webdna.us/page.dna?numero=3D55 Bug Reporting:=20 >> support@webdna.us > --------------------------------------------------------- This message=20 > is sent to you because you are subscribed to the mailing list=20 > talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us=20 > archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting:=20 > support@webdna.us=20 --=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 Oregon - www.GuideToOregon.com PO Box 1725, Jacksonville, OR 97530 California - www.OrangeCounty.net PO Box 2025, Capistrano Beach, CA 92624 --------------D94955073D44895F140DB2A4 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

Robert

I am in the process (expense) of moving a site=C2=A0 to an updated server, in order t= o 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 completel= y 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:<= br>
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.=C2=A0

= Robert Minor
= Cy= bermill.com
= 314-962-4024 ext 500

On Mar 1, 2018, at 07:52, Brian Willson <will= son@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@cyb= ermill.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.=C2=A0

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

On Mar 1, 2018, at 06:34, Brian Willson <willson@3ip.com&= gt; wrote:

Hey, everybody.

For years I=E2=80=99ve been u= sing [tcpconnect] to connect my online shopping carts with=C2=A0Autho= rize.net=E2=80=99s AIM solution, and it=E2=80=99s worked great= , with only a minor tweak or two required.

Yesterday, Authorize.net=C2=A0began 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 mak= e 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...

=C2=A0 =C2=A0[text show=3DF]response=3D[tcpconnect host=3D= s= ecure2.authorize.net&port=3D443&ssl=3DT]

...but simply using =E2=80=9C= ssl=3DF=E2=80=9D didn=E2=80=99t work, ha.

Here=E2=80=99s my main conn= ect code:

---

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

[/!][tcpsend]POST /gateway/transact.dll HTTP/1.0[crlf][!]

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

[/!]Host: s= ecure2.authorize.net:443[crlf][!]

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

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

[/!][crlf][!]

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

[/!][/tcpsend][/tcpconnec= t][/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-le= ave@webdna.us archives: http://= www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us<= /a>
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.u= s To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.we= bdna.us/page.dna?numero=3D55 Bug Reporting: support@webdn= a.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?nume= ro=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 

--=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
--------------------------------------------------------- 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 --------------D94955073D44895F140DB2A4-- . Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] TLS 1.2 and [tcpconnect] URGENT (Stuart Tremain 2018)
  2. Re: [WebDNA] TLS 1.2 and [tcpconnect] URGENT (Stuart Tremain 2018)
  3. Re: [WebDNA] TLS 1.2 and [tcpconnect] URGENT (Stuart Tremain 2018)
  4. Re: [WebDNA] TLS 1.2 and [tcpconnect] URGENT (Stuart Tremain 2018)
  5. Re: [WebDNA] TLS 1.2 and [tcpconnect] URGENT (Stuart Tremain 2018)
  6. Re: [WebDNA] TLS 1.2 and [tcpconnect] URGENT (Stuart Tremain 2018)
  7. Re: [WebDNA] TLS 1.2 and [tcpconnect] URGENT (Diane Blackmore 2018)
  8. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Diane Blackmore 2018)
  9. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Tom Duke 2018)
  10. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Diane Blackmore 2018)
  11. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Stuart Tremain 2018)
  12. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Jym Duane 2018)
  13. [WebDNA] TLS 1.2 and [tcpconnect] (Bob Knight 2018)
  14. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
  15. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
  16. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Jym Duane 2018)
  17. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
  18. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Jym Duane 2018)
  19. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
  20. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Jym Duane 2018)
  21. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
  22. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
  23. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
  24. Re: [WebDNA] TLS 1.2 and [tcpconnect] (christophe.billiottet@webdna.us 2018)
  25. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
  26. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
  27. Re: [WebDNA] TLS 1.2 and [tcpconnect] (dbrooke@euca.us 2018)
  28. Re: [WebDNA] TLS 1.2 and [tcpconnect] (dbrooke@euca.us 2018)
  29. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
  30. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
  31. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
  32. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
  33. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
  34. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
  35. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
  36. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Robert Minor 2018)
  37. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
  38. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Jym Duane 2018)
  39. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
  40. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
  41. Re: [WebDNA] TLS 1.2 and [tcpconnect] (Bob Minor 2018)
  42. [WebDNA] TLS 1.2 and [tcpconnect] (Brian Willson 2018)
1592 This is a multi-part message in MIME format. --------------D94955073D44895F140DB2A4 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Robert I am in the process (expense) of moving a site=C2=A0 to an updated server= , in=20 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=20 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=20 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=20 > thing with webdna on a newer server > > All I really do is read the post variables and resend them to authnet=20 > as another tcpconnect so to speak. But this would be running on an=20 > updated server. > > Robert Minor > Cybermill.com > 314-962-4024 ext 500 > > On Mar 1, 2018, at 07:52, Brian Willson > wrote: > >> Yikes. Sounds complicated. >> >> Is there no way to tweak the [tcpconnect] script to accommodate TLS=20 >> 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 >> > wrote: >>> >>> I got around it by running my own Linux server that does the php=20 >>> call to authnet and dumps the data just as the gateway did. kinda=20 >>> like a gateway for my gateway. >>> >>> Robert Minor >>> Cybermill.com >>> 314-962-4024 ext 500 >>> >>> On Mar 1, 2018, at 06:34, Brian Willson >> > wrote: >>> >>>> Hey, everybody. >>>> >>>> For years I=E2=80=99ve been using [tcpconnect] to connect my online=20 >>>> shopping carts with Authorize.net =E2=80=99s = AIM=20 >>>> solution, and it=E2=80=99s worked great, with only a minor tweak or = two=20 >>>> required. >>>> >>>> Yesterday, Authorize.net =C2=A0began requirin= g=20 >>>> connections via the TLS 1.2 protocol, and my script broke. I.e., it=20 >>>> can no longer connect to the endpoint. >>>> >>>> (I'd mistakenly assumed all I needed to do was make sure my server=20 >>>> supported TLS 1.2, duh.) >>>> >>>> Can anyone tell me how to make sure my script forces a connection=20 >>>> via TLS 1.2? >>>> >>>> I was hoping all I=E2=80=99d need is a tweak to this line... >>>> >>>> =C2=A0 =C2=A0[text show=3DF]response=3D[tcpconnect host=3Dsecure2.au= thorize.net=20 >>>> &port=3D443&ssl=3DT] >>>> >>>> ...but simply using =E2=80=9Cssl=3DF=E2=80=9D didn=E2=80=99t work, h= a. >>>> >>>> Here=E2=80=99s my main connect code: >>>> >>>> --- >>>> >>>> [text show=3DF]response=3D[tcpconnect host=3Dsecure2.authorize.net=20 >>>> &port=3D443&ssl=3DT][!] >>>> >>>> [/!][tcpsend]POST /gateway/transact.dll HTTP/1.0[crlf][!] >>>> >>>> [/!]User-Agent: e3IP[crlf][!] >>>> >>>> [/!]Host: secure2.authorize.net:443=20 >>>> [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=20 >>>> message is sent to you because you are subscribed to the mailing=20 >>>> list talk@webdna.us To unsubscribe, E-mail=20 >>>> to: talk-leave@webdna.us archives:=20 >>>> http://www.webdna.us/page.dna?numero=3D55 Bug Reporting:=20 >>>> support@webdna.us >>> --------------------------------------------------------- This=20 >>> message is sent to you because you are subscribed to the mailing=20 >>> list talk@webdna.us To unsubscribe, E-mail=20 >>> to: talk-leave@webdna.us archives:=20 >>> http://www.webdna.us/page.dna?numero=3D55 Bug Reporting:=20 >>> support@webdna.us >> >> --------------------------------------------------------- This=20 >> message is sent to you because you are subscribed to the mailing list=20 >> talk@webdna.us To unsubscribe, E-mail to:=20 >> talk-leave@webdna.us archives:=20 >> http://www.webdna.us/page.dna?numero=3D55 Bug Reporting:=20 >> support@webdna.us > --------------------------------------------------------- This message=20 > is sent to you because you are subscribed to the mailing list=20 > talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us=20 > archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting:=20 > support@webdna.us=20 --=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 Oregon - www.GuideToOregon.com PO Box 1725, Jacksonville, OR 97530 California - www.OrangeCounty.net PO Box 2025, Capistrano Beach, CA 92624 --------------D94955073D44895F140DB2A4 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

Robert

I am in the process (expense) of moving a site=C2=A0 to an updated server, in order t= o 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 completel= y 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:<= br>
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.=C2=A0

= Robert Minor
= Cy= bermill.com
= 314-962-4024 ext 500

On Mar 1, 2018, at 07:52, Brian Willson <will= son@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@cyb= ermill.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.=C2=A0

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

On Mar 1, 2018, at 06:34, Brian Willson <willson@3ip.com&= gt; wrote:

Hey, everybody.

For years I=E2=80=99ve been u= sing [tcpconnect] to connect my online shopping carts with=C2=A0Autho= rize.net=E2=80=99s AIM solution, and it=E2=80=99s worked great= , with only a minor tweak or two required.

Yesterday, Authorize.net=C2=A0began 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 mak= e 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...

=C2=A0 =C2=A0[text show=3DF]response=3D[tcpconnect host=3D= s= ecure2.authorize.net&port=3D443&ssl=3DT]

...but simply using =E2=80=9C= ssl=3DF=E2=80=9D didn=E2=80=99t work, ha.

Here=E2=80=99s my main conn= ect code:

---

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

[/!][tcpsend]POST /gateway/transact.dll HTTP/1.0[crlf][!]

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

[/!]Host: s= ecure2.authorize.net:443[crlf][!]

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

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

[/!][crlf][!]

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

[/!][/tcpsend][/tcpconnec= t][/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-le= ave@webdna.us archives: http://= www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us<= /a>
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.u= s To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.we= bdna.us/page.dna?numero=3D55 Bug Reporting: support@webdn= a.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?nume= ro=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 

--=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
--------------------------------------------------------- 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 --------------D94955073D44895F140DB2A4-- . Jym Duane

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:

Unexpected error (1997) (1998) Document Contains No Data! (1997) Help name our technology! I found it (1997) SiteGaurd file Cache vs webcatalog cache (1997) WebCat/PDF Integration Time Est (2000) Header info in content (1998) WCS Newbie question (1997) Newbie problem blah blah blah (1997) form data submission gets truncated (1997) Cookie set browser session. (1998) bypassing typo's (1998) [WebDNA] WebDNA 6.2 ErrorLog.txt (2014) two domains and one cart and database (2000) WebCat2 several catalogs? (1997) Problem with ShoppingCart.tpl refresh (2000) Math (1997) Ampersand (1997) ListWords passing multi values in one form field (2000) Combining Searches (1998)