E10060 with THttpClientSocket and not with Winhttp Client

itSDS · 2024-03-21 14:50:35

Hi i just switched from WinHttp to Socket client and get error 10060

Log Output

InternalUri GET
...
ESChannel {recv : Socket Error 10060}
ENetSocket {THttpClientSocket.DoTlsAfter: TLS failed ..

after a timeout of 30s

With WinHttp the connection can be established

We connect to a server with valid certificate.

I need a clou how to find the reason for the error- any thougths ?

ab · 2024-03-21 18:25:52

This is a timeout, probably at TCP level.

What is on the server side?
No proxy?
Does the client code work locally on the server itself?
Did you try enabling OpenSSL for the client instead of default SSPI?

Edit:
For client-side (aka mutual) authentication, you need to use OpenSSL, not SSPI.
The TNetTlsContext.ClientCertificateAuthentication flag is documented as 'not used on SChannel', i.e. not implemented.

itSDS · 2024-03-22 08:25:42

Ty just to give more information:

On Server Side Client Connection works in both modes.
Only Clients connecting over Network get timeout error

OpenSSL is disabled, I'll try it using OpenSSL

Last edited by itSDS (2024-03-22 08:25:54)

Chaa · 2024-03-22 09:13:58

Which Windows version you are use on client?

itSDS · 2024-05-14 09:56:57

Just to end this Ticket, with OPENSSL Version the Connection coulf be establiched.

One Thing: if i copy only the first dll (libcrypto...) and Libssl is missing, the Error Message should be like: libssl.. is missing ...

mORMot Open Source

#1 2024-03-21 14:50:35

E10060 with THttpClientSocket and not with Winhttp Client

#2 2024-03-21 18:25:52

Re: E10060 with THttpClientSocket and not with Winhttp Client

#3 2024-03-22 08:25:42

Re: E10060 with THttpClientSocket and not with Winhttp Client

#4 2024-03-22 09:13:58

Re: E10060 with THttpClientSocket and not with Winhttp Client

#5 2024-05-14 09:56:57

Re: E10060 with THttpClientSocket and not with Winhttp Client

Board footer