According to #1602, curl's timing behavior was changed to sum the values for each redirect when using -L. However, when a redirect results in a second DNS lookup and accesses a new IP address, it is not always useful to lump these times together, especially when timing resources which are served by CDN servers.
I expected the following
Curl should instead provide sequential timing information for each redirect separately.
Thanks, but this description sounds as if you're asking for a new feature/change. We use this tracker for bugs and issues only, we put ideas to work on in the future in the TODO document. We basically drown in good ideas so they don't do much use in our tracker.
If you really want to see this happen, start working on an implementation and submit a PR for it or join the mailing list and talk up more interest for it and see what help from others you can get!
I did this
According to #1602, curl's timing behavior was changed to sum the values for each redirect when using
-L
. However, when a redirect results in a second DNS lookup and accesses a new IP address, it is not always useful to lump these times together, especially when timing resources which are served by CDN servers.I expected the following
Curl should instead provide sequential timing information for each redirect separately.
curl/libcurl version
curl 7.68.0 (x86_64-pc-linux-gnu) libcurl/7.68.0 OpenSSL/1.1.1f zlib/1.2.11 brotli/1.0.7 libidn2/2.2.0 libpsl/0.21.0 (+libidn2/2.2.0) libssh/0.9.3/openssl/zlib nghttp2/1.40.0 librtmp/2.3
Release-Date: 2020-01-08
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: AsynchDNS brotli GSS-API HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM NTLM_WB PSL SPNEGO SSL TLS-SRP UnixSockets
operating system
Linux parmesan 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: