#1 2015-10-04 16:10:50

mpv
Member
From: Ukraine
Registered: 2012-03-24
Posts: 1,534
Website

TLS 1.2 support for TWinHTTP

We discover problems during connecting to HTTPS services with disabled TLS 1.0 (TLS1.2 only enabled) using TWinHTTP
So first I add ability do get exception message for such problems using WinHttpSetStatusCallback.
The second step is enable TLS1.1 & 1.2 using WinHttpSetOption with WINHTTP_OPTION_SECURE_PROTOCOLS.

So now we can connect to modern-secure HTTPS services. See http://synopse.info/fossil/info/5f833a7 … e5dfcc5156

Offline

#2 2015-10-05 10:01:12

ab
Administrator
From: France
Registered: 2010-06-21
Posts: 14,183
Website

Re: TLS 1.2 support for TWinHTTP

Thanks a lot for sharing!

We fixed the patch for working with older versions of Delphi, and with FPC.

Offline

#3 2015-10-05 10:39:00

mpv
Member
From: Ukraine
Registered: 2012-03-24
Posts: 1,534
Website

Re: TLS 1.2 support for TWinHTTP

Oops. My mistake. I'll try to be more attentive

Offline

#4 2015-10-05 12:06:50

ab
Administrator
From: France
Registered: 2010-06-21
Posts: 14,183
Website

Re: TLS 1.2 support for TWinHTTP

No problem, that's fine.
smile

Offline

#5 2015-10-05 18:02:44

ab
Administrator
From: France
Registered: 2010-06-21
Posts: 14,183
Website

Re: TLS 1.2 support for TWinHTTP

I forgot to merge...

But what is the point of changing the default SynSM global JavaScript object from "global" to "Window"?
There is no DOM in SynSM, AFAIR.
See http://synopse.info/fossil/info/d18f9f8e1e

Offline

#6 2015-10-05 19:15:14

mpv
Member
From: Ukraine
Registered: 2012-03-24
Posts: 1,534
Website

Re: TLS 1.2 support for TWinHTTP

You are right - must be "global", of course. This unit must not be committed. But I can't found how to do something like "rebase" in fossil and confused with fossil merge.

Offline

Board footer

Powered by FluxBB