Re: [WebDNA] TLS 1.2 and [tcpconnect]

This WebDNA talk-list message is from

2018


It keeps the original formatting.
numero = 114023
interpreted = N
texte = 1623 This is a multi-part message in MIME format. --------------6F26D8E89CDE8FA1B40A6602 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable I have now moved a site to latest Centos, apache, webdna with valid=20 security certificate that checks out when tested that all is well. A=20 rating and TLS 1.2 everything on site is now working , except so far can not complete the transaction part through the tcp conne= ct. im hoping when i get login info to clients anet account i can see whats=20 happenng, and that i can add the new sending IP to anet in case that is=20 the issue, tons of work so far all needed, but would be real diapointing if it does=20 not work withi webdna as is. jym On 3/4/2018 8:18 AM, Bob Knight wrote: > I have a question regarding this as well. > > So after my shipping and creditcard processing stopped working after=20 > the TLS 1.2 update from UPS and Authorize.net =20 > occurred. I discovered it is time to update the server to the newer OS=20 > X 10.12 and the webdna version WebDNA Server 8.5.1 for Apple OS X=20 > Sierra . =A0Now that I hav= e=20 > done that and everything appears to be working, I am still unable to=20 > connect to these third party servers using the [tcpconnect] [tcpsend]=20 > parameters that normally worked for the last 15 years. =A0I tested the=20 > connection to the third party servers using a standard PHP connection=20 > from this same (newly installed server) via a test.php page within the=20 > same website and the connection works fine. =A0But the PHP post is a=20 > different setup from the WEBDNA setup so I am not sure the comparison=20 > is actually a good test. =A0But it does show that the TLS 1.2 is workin= g=20 > to the third party servers so I am confident that the Apache and OS X=20 > servers are setup properly. =A0 =A0So it leads me to believe their is=20 > something not working correctly within the WEBDNA server when it comes=20 > to the [tcpconnect] [tcpsend] protocol. > > So in anyones opinion, is it the OS X, the Apache, [webdna 8.5.1] that=20 > is keeping the [tcpconnect] [tcpsend] =A0command from working with thir= d=20 > party servers? > > > [tcpconnect host=3Dinternic.net &portC] > [tcpsend] webdna.us=20 > [unurl] %= 0D%0A%0D%0A[/unurl][/tcpsend] > [/tcpconnect] > > --------------------------------------------------------- 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 --------------6F26D8E89CDE8FA1B40A6602 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable

I have now moved a sit= e to latest Centos, apache, webdna with valid security certificate that checks out when tested that all is well. A rating and TLS 1.2

everything on site is now working ,

except so far can not complete the transaction part through the tcp connect.

im hoping when i get l= ogin info to clients anet account i can see whats happenng, and that i can add the new sending IP to anet in case that is the issue,

tons of work so far al= l needed, but would be real diapointing if it does not work withi webdna as is.

jym


On 3/4/2018 8:18 AM, Bob Knight wrote:=
I have a question regarding this as well.

So after my shipping and creditcard processing stopped working after the TLS 1.2 update from UPS and Authorize.net occurred. I discovered it is time to update the server to the newer OS X 10.12 and the webdna version=A0WebD= NA Server 8.5.1 for Apple OS X Sierra. =A0Now that I have done that and everything appears to be working, I am still unable to connect to these third party servers using the [tcpconnect] [tcpsend] parameters that normally worked for the last 15 years. =A0I tested the connection to the third party servers using a standard PHP connection from this same (newly installed server) via a test.php page within the same website and the connection works fine. =A0But the PHP post is a different setup from the WEBDNA setup so I am not sure the comparison is actually a good test. =A0But it does show that the TLS 1.2 is working to the thir= d party servers so I am confident that the Apache and OS X servers are setup properly. =A0 =A0So it leads me to believe their is something not working correctly within the WEBDNA server when it comes to the [tcpconnect] [tcpsend] protocol.=A0

So in anyones opinion, is it the OS X, the Apache, [webdna 8.5.1] that is keeping the [tcpconnect] [tcpsend] =A0command from working with third party servers?


[tcpconnect host=3Dinternic.net&portC][tcpsend]webdna.us[unurl]%0D%=0A%0D%0A[/unurl][/tcpsend][/tcpconnect]

--------------------------------------------------------- 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 --------------6F26D8E89CDE8FA1B40A6602-- . 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)
1623 This is a multi-part message in MIME format. --------------6F26D8E89CDE8FA1B40A6602 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable I have now moved a site to latest Centos, apache, webdna with valid=20 security certificate that checks out when tested that all is well. A=20 rating and TLS 1.2 everything on site is now working , except so far can not complete the transaction part through the tcp conne= ct. im hoping when i get login info to clients anet account i can see whats=20 happenng, and that i can add the new sending IP to anet in case that is=20 the issue, tons of work so far all needed, but would be real diapointing if it does=20 not work withi webdna as is. jym On 3/4/2018 8:18 AM, Bob Knight wrote: > I have a question regarding this as well. > > So after my shipping and creditcard processing stopped working after=20 > the TLS 1.2 update from UPS and Authorize.net =20 > occurred. I discovered it is time to update the server to the newer OS=20 > X 10.12 and the webdna version WebDNA Server 8.5.1 for Apple OS X=20 > Sierra . =A0Now that I hav= e=20 > done that and everything appears to be working, I am still unable to=20 > connect to these third party servers using the [tcpconnect] [tcpsend]=20 > parameters that normally worked for the last 15 years. =A0I tested the=20 > connection to the third party servers using a standard PHP connection=20 > from this same (newly installed server) via a test.php page within the=20 > same website and the connection works fine. =A0But the PHP post is a=20 > different setup from the WEBDNA setup so I am not sure the comparison=20 > is actually a good test. =A0But it does show that the TLS 1.2 is workin= g=20 > to the third party servers so I am confident that the Apache and OS X=20 > servers are setup properly. =A0 =A0So it leads me to believe their is=20 > something not working correctly within the WEBDNA server when it comes=20 > to the [tcpconnect] [tcpsend] protocol. > > So in anyones opinion, is it the OS X, the Apache, [webdna 8.5.1] that=20 > is keeping the [tcpconnect] [tcpsend] =A0command from working with thir= d=20 > party servers? > > > [tcpconnect host=3Dinternic.net &portC] > [tcpsend] webdna.us=20 > [unurl] %= 0D%0A%0D%0A[/unurl][/tcpsend] > [/tcpconnect] > > --------------------------------------------------------- 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 --------------6F26D8E89CDE8FA1B40A6602 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable

I have now moved a sit= e to latest Centos, apache, webdna with valid security certificate that checks out when tested that all is well. A rating and TLS 1.2

everything on site is now working ,

except so far can not complete the transaction part through the tcp connect.

im hoping when i get l= ogin info to clients anet account i can see whats happenng, and that i can add the new sending IP to anet in case that is the issue,

tons of work so far al= l needed, but would be real diapointing if it does not work withi webdna as is.

jym


On 3/4/2018 8:18 AM, Bob Knight wrote:=
I have a question regarding this as well.

So after my shipping and creditcard processing stopped working after the TLS 1.2 update from UPS and Authorize.net occurred. I discovered it is time to update the server to the newer OS X 10.12 and the webdna version=A0WebD= NA Server 8.5.1 for Apple OS X Sierra. =A0Now that I have done that and everything appears to be working, I am still unable to connect to these third party servers using the [tcpconnect] [tcpsend] parameters that normally worked for the last 15 years. =A0I tested the connection to the third party servers using a standard PHP connection from this same (newly installed server) via a test.php page within the same website and the connection works fine. =A0But the PHP post is a different setup from the WEBDNA setup so I am not sure the comparison is actually a good test. =A0But it does show that the TLS 1.2 is working to the thir= d party servers so I am confident that the Apache and OS X servers are setup properly. =A0 =A0So it leads me to believe their is something not working correctly within the WEBDNA server when it comes to the [tcpconnect] [tcpsend] protocol.=A0

So in anyones opinion, is it the OS X, the Apache, [webdna 8.5.1] that is keeping the [tcpconnect] [tcpsend] =A0command from working with third party servers?


[tcpconnect host=3Dinternic.net&portC][tcpsend]webdna.us[unurl]%0D%=0A%0D%0A[/unurl][/tcpsend][/tcpconnect]

--------------------------------------------------------- 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 --------------6F26D8E89CDE8FA1B40A6602-- . 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:

Many $WebCat.exe processes (1998) [isfile] ? (1997) Replace context problem ... (1997) Summing fields (1997) Variable prices and Formulas.db (1997) WebDNA deletes major DB data big time (2004) Re:no [search] with NT (1997) Exclamation point (1997) web delivery (1997) Interesting speed comparison .. (2003) Setting up shop (1997) RE: new cart IDs being assigned somehow (1997) Problems adding stuff to the shopping cart. (1997) Upcoming 2.1 Release and PCS Committment (1997) WebCatalog Hosting (1996) Sticky .inc file! (2008) addlineitems (2003) My web page only... (2003) [WebDNA] 6.2.1 fails on Apache 2.4.6 (2014) NT or Mac (1998)