On 5 Mar 2018, at 03:18, Bob Knight <bobioknight@gmail.com> wrote:I have a =question regarding this as well.---------------------------------------------------------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.usSo 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]
On 5 Mar 2018, at 03:18, Bob Knight <bobioknight@gmail.com> wrote:I have a =question regarding this as well.---------------------------------------------------------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.usSo 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]
DOWNLOAD WEBDNA NOW!
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...