Re: HTTP authentication negotiation
Date: Wed, 4 Jun 2008 11:59:53 +0200 (CEST)
On Wed, 4 Jun 2008, Raf Nulens wrote:
> PUT /pres-rules/users/test04_at_androme.com/pres-rules HTTP/1.1
> Expect: 100-continue
> HTTP/1.1 100 Continue
> [full body]
> HTTP/1.1 401 Unauthorized
Welcome to a world full of brain-dead HTTP servers that act like this. The
100-continue is designed to allow the server to reject the data before the
client sends it, but far too many servers just blindly send 100 first only to
reject it once the data has been sent...
> Is there any option we can set so that libcurl resends the PUT request (with
> authentication) after the 401 unauthorized response, or is this logic
> implemented outside libcurl?
CURLOPT_SOCKOPTFUNCTION is the option you're looking for. You need to provide
the seek/rewind function to allow libcurl to seek back to the beginning.
> Second question: we know that the server where we send the PUT request to
> needs authentication (either digest or basic), so we expect to get a 401
> response after the first PUT. When we set CURLOPT_HTTPAUTH to
> CURLAUTH_DIGEST, we see that the first PUT is sent with content-length: 0
> and without "Expect: 100-continue". However when we set CURLOPT_HTTPAUTH to
> CURLAUTH_BASIC | CURLAUTH_DIGEST, the first PUT is sent with content-length:
> 279 and Expect: 100-continue (as seen in the trace).
> Shouldnt libcurl make a difference between CURLAUTH_BASIC | CURLAUTH_DIGEST
> and CURLAUTH_NONE | CURLAUTH_BASIC | CURLAUTH_DIGEST?
Possibly, but as I recall things the logic is like this:
If you set multiple HTTP auth methods allowed, libcurl enables "auth probe
mode" that is pretty much indepdendent on what protocols you allow, and then
it sends the first request to allow none as well. In fact, the CURLAUTH_NONE
define is 0 so libcurl can't even detect when you explictly allow it (or not).
Then, when the response comes back saying it didn't accept "no auth", libcurl
will use your set preference and the server's response headers to pick the
suitable method to proceed with.
I could imagine allowing a more strict use of NONE to enable no auth like you
say, but that would take some poking of libcurl internals.
-- / daniel.haxx.seReceived on 2008-06-04