Re: [WebDNA] TLS 1.2 and [tcpconnect] URGENT

This WebDNA talk-list message is from

2018


It keeps the original formatting.
numero = 114281
interpreted = N
texte = 1886 --Apple-Mail=_4F7C346D-9761-46BE-B528-8E62F03AF210 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Check that you have curl on the server. Go to cl and type curl =E2=80=94version or=20 curl https://google.com if you get a response all is good. then just build your curl segment in the cl, once it is working transfer = it to your site I suspect that it will work something like this: [SHELL]curl = https:/www.paystation.co.nz//direct/paystation.dll?all-your-variables-here= [/SHELL] Unless you are posting an xml file, then you will need to use some = different curl code Kind regards Stuart Tremain Pharoah Lane Software AUSTRALIA webdna@plsoftware.com.au > On 1 Jun 2018, at 10:25, Diane Blackmore wrote: >=20 > Hi >=20 > 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. >=20 > 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. >=20 > 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. >=20 >=20 > Thanks, >=20 > > >> On 28/05/2018, at 9:53 PM, Tom Duke > wrote: >>=20 >> Diane, >>=20 >> If your server supports the correct version of TLS then the SSL = connection should be good. There is no "TLS=3DT" option with = TCPConnect. >>=20 >> Also you might consider using 'curl' in a [shell] command. I stopped = using TCPConnect a long time ago. >>=20 >> - Tom >>=20 >>=20 >>=20 >>=20 >>=20 >> =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]: > >> [w]: > >> =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 >>=20 >> On 28 May 2018 at 02:40, Diane Blackmore > wrote: >> Hi >>=20 >> 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; >>=20 >> [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] >>=20 >> 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. >>=20 >> 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? >>=20 >> Thanks in advance, >>=20 >> >> >> >>> On 5/03/2018, at 11:32 AM, Stuart Tremain > wrote: >>>=20 >>> That looks like an error in the docs >>>=20 >>> it should read &port=3D80 or port=3D443 >>>=20 >>>=20 >>>=20 >>> Kind regards >>>=20 >>> Stuart Tremain >>> Pharoah Lane Software >>> AUSTRALIA >>> webdna@idfk.com.au >>>=20 >>>=20 >>>=20 >>>=20 >>>=20 >>>=20 >>>> On 5 Mar 2018, at 03:18, Bob Knight > wrote: >>>>=20 >>>> I have a question regarding this as well. >>>>=20 >>>> 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 >>>>=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? >>>>=20 >>>>=20 >>>> [tcpconnect host=3Dinternic.net &portC] >>>> [tcpsend] webdna.us = [unurl] = %0D%0A%0D%0A[/unurl][/tcpsend]= >>>> [/tcpconnect] >>>>=20 >>>> --------------------------------------------------------- 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 >>> --------------------------------------------------------- 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 >> --------------------------------------------------------- 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 >> --------------------------------------------------------- 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 > --------------------------------------------------------- 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=_4F7C346D-9761-46BE-B528-8E62F03AF210 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Check= that you have curl on the server.
Go to cl and type curl = =E2=80=94version

or 



if = you get a response all is good.

then just build your curl segment in = the cl, once it is working transfer it to your site

I suspect that it will = work something like this:



Unless you are posting an xml file, then you will need to = use some different curl code


Kind regards

Stuart Tremain
Pharoah Lane Software
AUSTRALIA







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,


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][!]
[/!]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,


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






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

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

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

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

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

= --------------------------------------------------------- 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=_4F7C346D-9761-46BE-B528-8E62F03AF210-- . 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)
1886 --Apple-Mail=_4F7C346D-9761-46BE-B528-8E62F03AF210 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Check that you have curl on the server. Go to cl and type curl =E2=80=94version or=20 curl https://google.com if you get a response all is good. then just build your curl segment in the cl, once it is working transfer = it to your site I suspect that it will work something like this: [shell]curl = https:/www.paystation.co.nz//direct/paystation.dll?all-your-variables-here= [/SHELL] Unless you are posting an xml file, then you will need to use some = different curl code Kind regards Stuart Tremain Pharoah Lane Software AUSTRALIA webdna@plsoftware.com.au > On 1 Jun 2018, at 10:25, Diane Blackmore wrote: >=20 > Hi >=20 > 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. >=20 > 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. >=20 > 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. >=20 >=20 > Thanks, >=20 > > >> On 28/05/2018, at 9:53 PM, Tom Duke > wrote: >>=20 >> Diane, >>=20 >> If your server supports the correct version of TLS then the SSL = connection should be good. There is no "TLS=3DT" option with = TCPConnect. >>=20 >> Also you might consider using 'curl' in a [shell] command. I stopped = using TCPConnect a long time ago. >>=20 >> - Tom >>=20 >>=20 >>=20 >>=20 >>=20 >> =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]: > >> [w]: > >> =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 >>=20 >> On 28 May 2018 at 02:40, Diane Blackmore > wrote: >> Hi >>=20 >> 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; >>=20 >> [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] >>=20 >> 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. >>=20 >> 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? >>=20 >> Thanks in advance, >>=20 >> >> >> >>> On 5/03/2018, at 11:32 AM, Stuart Tremain > wrote: >>>=20 >>> That looks like an error in the docs >>>=20 >>> it should read &port=3D80 or port=3D443 >>>=20 >>>=20 >>>=20 >>> Kind regards >>>=20 >>> Stuart Tremain >>> Pharoah Lane Software >>> AUSTRALIA >>> webdna@idfk.com.au >>>=20 >>>=20 >>>=20 >>>=20 >>>=20 >>>=20 >>>> On 5 Mar 2018, at 03:18, Bob Knight > wrote: >>>>=20 >>>> I have a question regarding this as well. >>>>=20 >>>> 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 >>>>=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? >>>>=20 >>>>=20 >>>> [tcpconnect host=3Dinternic.net &portC] >>>> [tcpsend] webdna.us = [unurl] = %0D%0A%0D%0A[/unurl][/tcpsend]= >>>> [/tcpconnect] >>>>=20 >>>> --------------------------------------------------------- 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 >>> --------------------------------------------------------- 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 >> --------------------------------------------------------- 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 >> --------------------------------------------------------- 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 > --------------------------------------------------------- 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=_4F7C346D-9761-46BE-B528-8E62F03AF210 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Check= that you have curl on the server.
Go to cl and type curl = =E2=80=94version

or 



if = you get a response all is good.

then just build your curl segment in = the cl, once it is working transfer it to your site

I suspect that it will = work something like this:



Unless you are posting an xml file, then you will need to = use some different curl code


Kind regards

Stuart Tremain
Pharoah Lane Software
AUSTRALIA







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,


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,


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






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

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

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

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

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

= --------------------------------------------------------- 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=_4F7C346D-9761-46BE-B528-8E62F03AF210-- . Stuart Tremain

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:

select multiple 2 more cents (1997) Nesting format tags (1997) Snake Bites (1997) POST Datamissing? (1998) WebCat2 several catalogs? (1997) Remove Command not working (2000) [taxRate] [TaxTotal] ? (1997) Email within tmpl ? (1997) Separate SSL Server (1997) WebCat2b13MacPlugin - nested [xxx] contexts (1997) [WebDNA] A new popuated field to a DB with 700.000 records (2009) WebCatalog2 Feature Feedback (1996) searchable list archive (1997) Training Videos for 3.0 (1998) problems with 2 tags (1997) Max Record length restated as maybe bug (1997) WebCatalog2 Feature Feedback (1996) FAX orders (1996) How to add product size choices to form? (1997) Weird bug, or is there something amiss? (1997)