-
-
Notifications
You must be signed in to change notification settings - Fork 6.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug NTLM authentication wrong behavior with the head flag --head or -I #13674
Comments
If you add 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... |
No response |
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: