Buy commercial curl support. We
help you work out your issues, debug your libcurl applications, use the API,
port to new platforms, add new features and more. With a team lead by the
curl founder Daniel himself.
curl mutually exclusive --ntlm and --negotiate option
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: jicea via curl-users <curl-users_at_lists.haxx.se>
Date: Mon, 28 Jul 2025 11:14:11 +0000
Hi all,
I've a simple questions regarding --ntlm and --negotiate option. In the manual for ntlm, it is written that "--ntlm requires that libcurl is built to support TLS. This option is mutually exclusive with --basic, --negotiate, --digest and --anyauth. See also --proxy-ntlm."
I find regardless a lot of examples on web search that use the two options together for instance "curl -X POST -k -v --ntlm --negotiate -u usernamehere -F "csv=_at_pt_update.csv" -F "op=add" "https://google.com/csv_import""
My questions is:
- Are --ntlm and --negotiate exclusive? if yes, what's the choosen one if both options are provided?
- mutual exclusive options like negotiate and ntlm seems to be accepted in cli (I can write "curl --negotiate --ntlm --user "" --verbose foo.com" without error). Is the "mutual exclusive" just a doc hint or is there any mechanism that raises an error if user uses mutual exclusives option?
Thanks a lot,
Jean-Christophe
Orange Restricted
____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
Date: Mon, 28 Jul 2025 11:14:11 +0000
Hi all,
I've a simple questions regarding --ntlm and --negotiate option. In the manual for ntlm, it is written that "--ntlm requires that libcurl is built to support TLS. This option is mutually exclusive with --basic, --negotiate, --digest and --anyauth. See also --proxy-ntlm."
I find regardless a lot of examples on web search that use the two options together for instance "curl -X POST -k -v --ntlm --negotiate -u usernamehere -F "csv=_at_pt_update.csv" -F "op=add" "https://google.com/csv_import""
My questions is:
- Are --ntlm and --negotiate exclusive? if yes, what's the choosen one if both options are provided?
- mutual exclusive options like negotiate and ntlm seems to be accepted in cli (I can write "curl --negotiate --ntlm --user "" --verbose foo.com" without error). Is the "mutual exclusive" just a doc hint or is there any mechanism that raises an error if user uses mutual exclusives option?
Thanks a lot,
Jean-Christophe
Orange Restricted
____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-users Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2025-07-28