#1477 time_connect not set when using ntlm authentication

[Matt]

When connecting to a service which requires NTLM authentication the time_connect value is always returned 0.000.

curl --ntlm -u DOMAIN\USERNAME:PASSWORD -v -w %{time_connect} http://some-ntlm-service.com:80/Shared/SomeReportPage.htm

Current version: running linux
curl 7.35.0 (x86_64-pc-linux-gnu) libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2.3
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp smtp smtps telnet tftp
Features: AsynchDNS GSS-Negotiate IDN IPv6 Largefile NTLM NTLM_WB SSL libz TLS-SRP

Also reproducible on windows

[Matt]

If a project admin would like some credentials to test I can mail you some. Please let me know.

[Daniel Stenberg]

Can you please re-resubmit this problem in the new bug tracker we've moving to? We're closing this down and I would like to get all "active" bugs moved over and yet I don't have any way to do it automatically.

You can still link to this bug report as it won't vanish, we'll just focus all activities going forward on the new one.

The new bug tracker: https://github.com/bagder/curl/issues