cURL / Mailing Lists / curl-library / Single Mail


Re: Connection getting closed on receiving 401 from server during POST

From: Daniel Stenberg <>
Date: Mon, 14 Jul 2014 19:43:13 +0200 (CEST)

On Mon, 16 Jun 2014, Vivek S wrote:

> So in this second mode, we don't have option to use curl's NTLM option as we
> don't have credentials; but have to maintain the connection for NTLM
> handshake to complete. This is the point where libcurl closes the connection
> on seeing 401 (when receiving NTLM challenge-2) and making NTLM
> authentication to fail during POST/OPTIONS requests.
> I think, I can generalize the problem as current libcurl cannot proxy (in
> sense, relaying the data) NTLM authentications in all requests methods.

I get it. You basically want a new option that tells libcurl to pretend NTLM
is in use - more or less - so that it maintains the connection with a higher
precedence than it does now. I can't see that we currently have any option
that makes libcurl do this...

List admin:
Received on 2014-07-14