On Mon, 12 Nov 2007, pangot_at_degetel.com wrote:

> But it's not correct to tell that LibCurl supports HTTP
> Digest Authentication on the main LibCurl web page...

Yes it is correct, because it supports Digest and works fine for a large
amount of people.

But no, it doesn't support everything in the Digest spec.

Me knowingly, there's no certificate or license to apply for for Digest
compliance so we are allowed to claim that we support it as much as we want.
Saying we _don't_ support Digest when we in fact support the most commonly
used variations of it (I have no numbers backing this up, it is just my gut
feeling) would be even worse IMHO.

And BTW, it is also not correct to top-post on a mailing list where it is
strictly asked not to.

So instead of being a smart-ass, do you want to help us achieve better (full?)
compliance with the Digest spec? (As far as I recall the situation, the code
you're "bashing" was written entirely by me on my own spare time with no
financial backing at all.)

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html