2018

On 1 Jun 2018, at 10:25, Diane Blackmore <diane@cohesion.co.nz> wrote:

Hi

Anyone have a curl =written for this in WebDNA as a shell command yet? I=E2=80=99m scared as =heck that my provider is going to switch off support for below TLS 1.2 =and my TCP/IP connect is going to fail after reading earlier posts on =the matter.

I =have a client who does multiple orders per hour and this isn=E2=80=99t =going to go down well if I can=E2=80=99t get the payment gateway working ==E2=80=98cos I don=E2=80=99t know jack about curl.

Happy to pay someone for =this - I can supply you the WebDNA TCP/IP and a development site for you =to work on. But its URGENT please.

Thanks,

<CohesionSig_Diane12.gi=f>




On 28/05/2018, at 9:53 PM, Tom Duke <tom@revolutionaries.ie> wrote:

Diane,

If =your server supports the correct version of TLS then the SSL connection =should be good.  There is no "TLS=3DT" option with =TCPConnect.

Also= you might consider using 'curl' in a [shell] command.  I stopped =using TCPConnect a long time ago.

- Tom

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D
Digital Revolutionaries
1st Floor, =Castleriver House
14-15 Parliament Street
Temple Bar,Dublin 2
Ireland
----------------------------------------------
[t]: + 353 1 4403907
[e]: <mailto:tom@revolutionaries.ie>
[w]: <http://www.revolutionaries.ie/>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=



On 28 May 2018 at 02:40, Diane =Blackmore <diane@cohesion.co.nz> wrote:

Hi

Have finally got things to where they =need to be server-wise for my TLS 1.2 migration, however it is timing =out and not getting anywhere. The bolo is the script;

[TCPConnect host=3Dwww.paystation.co.nz&port=3D443&tls=3DT][tcpsend skipheader=3DT][!]

[/!]POST /direct/paystation.dll HTTP/1.1[crlf][!]

[/!]Referer: https://[theDomain][thisURL][crlf][!]

[/!]Host: www.paystation.co.nz[crlf][!]

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

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

[/!]Connection: =close[crlf][!]

[/!][crlf][!]

[/!][the_variables][crlf][!]

[/!][/tcpsend][/TCPConnect]

Now, this works just brilliant with =SSL=3DT in place of TLS=3DT but just hangs the way it is above. I figure =I must be missing something - Can anyone provide the correct syntax as =there=E2=80=99s nothing in the docs about TLS at all.

One other thought is =that the page doing the sending is a regular page on http/80, rather =than being on https/443 - Does this have any bearing? Ie. Would the =request also need to be from a secure site?

Thanks in advance,

<CohesionSig_Diane12.gif>




On 5/03/2018, at 11:32 AM, Stuart Tremain =<webdna@idfk.com.au> wrote:

That looks like an error in the docs

it should read   &port=3D80 = or   port=3D443



Kind regards

Stuart Tremain

Pharoah Lane Software

AUSTRALIA

webdna@idfk.com.au





On 5 Mar 2018, at 03:18, Bob Knight <bobioknight@gmail.com> 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 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 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

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