[WebDNA] TLS 1.2 and [tcpconnect]

This WebDNA talk-list message is from

2018


It keeps the original formatting.
numero = 114022
interpreted = N
texte = 1622 --Apple-Mail=_10998FAE-4078-4A5D-B975-335BA42AD467 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii 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 = WebDNA Server 8.5.1 for Apple OS X Sierra = . Now 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. I 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. But the PHP post is a different setup from = the WEBDNA setup so I am not sure the comparison is actually a good = test. But it does show that the TLS 1.2 is working to the third party = servers so I am confident that the Apache and OS X servers are setup = properly. So it leads me to believe their is something not working = correctly within the WEBDNA server when it comes to the [tcpconnect] = [tcpsend] protocol.=20 So in anyones opinion, is it the OS X, the Apache, [webdna 8.5.1] that = is keeping the [tcpconnect] [tcpsend] command from working with third = party servers? [tcpconnect host=3Dinternic.net&portC] [tcpsend] webdna.us[unurl] = %0D%0A%0D%0A[/unurl][/tcpsend]= [/tcpconnect] --Apple-Mail=_10998FAE-4078-4A5D-B975-335BA42AD467 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii 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 WebDNA = Server 8.5.1 for Apple OS X Sierra.  Now 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.  I 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.  But the PHP post is a = different setup from the WEBDNA setup so I am not sure the comparison is = actually a good test.  But it does show that the TLS 1.2 is working = to the third party servers so I am confident that the Apache and OS X = servers are setup properly.    So it leads me to believe their = is something not working correctly within the WEBDNA server when it = comes to the [tcpconnect] [tcpsend] protocol. 

So in anyones opinion, = is it the OS X, the Apache, [webdna 8.5.1] that is keeping the = [tcpconnect] [tcpsend]  command 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 --Apple-Mail=_10998FAE-4078-4A5D-B975-335BA42AD467-- . 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)
1622 --Apple-Mail=_10998FAE-4078-4A5D-B975-335BA42AD467 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii 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 = WebDNA Server 8.5.1 for Apple OS X Sierra = . Now 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. I 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. But the PHP post is a different setup from = the WEBDNA setup so I am not sure the comparison is actually a good = test. But it does show that the TLS 1.2 is working to the third party = servers so I am confident that the Apache and OS X servers are setup = properly. So it leads me to believe their is something not working = correctly within the WEBDNA server when it comes to the [tcpconnect] = [tcpsend] protocol.=20 So in anyones opinion, is it the OS X, the Apache, [webdna 8.5.1] that = is keeping the [tcpconnect] [tcpsend] command from working with third = party servers? [tcpconnect host=3Dinternic.net&portC] [tcpsend] webdna.us[unurl] = %0D%0A%0D%0A[/unurl][/tcpsend]= [/tcpconnect] --Apple-Mail=_10998FAE-4078-4A5D-B975-335BA42AD467 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii 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 WebDNA = Server 8.5.1 for Apple OS X Sierra.  Now 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.  I 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.  But the PHP post is a = different setup from the WEBDNA setup so I am not sure the comparison is = actually a good test.  But it does show that the TLS 1.2 is working = to the third party servers so I am confident that the Apache and OS X = servers are setup properly.    So it leads me to believe their = is something not working correctly within the WEBDNA server when it = comes to the [tcpconnect] [tcpsend] protocol. 

So in anyones opinion, = is it the OS X, the Apache, [webdna 8.5.1] that is keeping the = [tcpconnect] [tcpsend]  command 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 --Apple-Mail=_10998FAE-4078-4A5D-B975-335BA42AD467-- . Bob Knight

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:

WebCatalog 4.0 has been released! (2000) Capturing the referring site (1999) What about that Cc and Bcc bug? (2000) Shopping Cart ID (1998) Web Catalog and Net Cloak (1998) problem (1998) Help need to figure this out today!!! Advanced Question. (2004) Logging purchases (1997) Max Record length restated as maybe bug (1997) Email Attachments (1998) Internet Explorer 6 Form problems (2005) Re:my First Ship table (1998) [FoundItems] solved - thanks (1997) hierarchy question... (2000) Referrer field to header field conversion (1997) [WriteFile] problems (1997) Merchant and WebCat 3.0 (1998) Answer: WebDelivery downloads alias, not original ? (1997) includes and cart numbers (1997) Bit off subject -- Faxing orders (1997)