You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you add --trace-config write to the command line you will get added tracing information for the writing of download data.
I suspect that trace output will show that the HEAD requests actually get body data back and that curl consider that an error (it is a protocol violation) and marks the connection for close. Since NTLM authenticates connections, the next request then starts a new connection and the NTLM auth has to start over again...
I did this
Trying to authenticate against an NTLM endpoint with the -I flag. Here the command seems to forget the received header from the server.
I expected the following
When explicitly using the request flag and setting it to HEAD the authentication works as expected:
curl/libcurl version
operating system
Arch Linux
The text was updated successfully, but these errors were encountered: