Description
time_connect is 0 when error
I did this
I can connect to 1.1.1.1
:
curl "https://1.1.1.1" --output nul --write-out "%{time_connect}" --no-progress-meter -slient
time_connect
here is > 0.
Deliberately point example.com
to 1.1.1.1
to cause a ssl error:
curl "https://example.com" --output nul --write-out "%{time_connect}" --no-progress-meter --resolve "example.com:443:1.1.1.1" -slient
time_connect
here is 0.000000
on 7.88
, > 0 on 7.87
.
I expected the following
time_connect
> 0.
curl/libcurl version
curl 7.88.1 (x86_64-w64-mingw32) libcurl/7.88.1 OpenSSL/3.0.8 (Schannel) zlib/1.2.13 brotli/1.0.9 zstd/1.5.4 WinIDN libssh2/1.10.0 nghttp2/1.52.0 ngtcp2/0.13.1 nghttp3/0.8.0 libgsasl/2.2.0
Release-Date: 2023-02-20
Protocols: dict file ftp ftps gopher gophers http https imap imaps ldap ldaps mqtt pop3 pop3s rtsp scp sftp smb smbs smtp smtps telnet tftp ws wss
Features: alt-svc AsynchDNS brotli gsasl HSTS HTTP2 HTTP3 HTTPS-proxy IDN IPv6 Kerberos Largefile libz MultiSSL NTLM SPNEGO SSL SSPI threadsafe TLS-SRP UnixSockets zstd
operating system
Microsoft Windows [Version 10.0.19045.2673]