On Mon, 19 Feb 2007, Achint Mehta wrote:

> You are right. In a perfect world the web-server would respond back with
> 401, since the nonce value would not be valid anymore ( and possibly set the
> stale true if the request is for the same URL). This is not a bug on the
> libcurl side, but when I saw this behaviour I thought that we might be
> forgetting to clear the previous Authorization header.

Thanks for your efforts.

I must admit I don't fully understand the implications of what you wrote. (It
was a while since I looked at that part of the code.)

Can you make a complete patch to really visualize to me/us what you suggest?

> On a separate note, I (and almost everyone would ) have found libcurl to be
> a swiss knife. It is extremely simple yet vast in functionality. Even the
> code has been very modularised and well commented making it easy to
> understand. I had to go into the libcurl code for some trivial things and I
> do apprecaite the neatness of the code which saved me lots of time and
> trouble.

Thank you!

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