Well, isn't that fancy.... Somewhat easier to read than the raw tcpdump
output....

> What curl version is this? I trust you at least tried this with the
> latest version to make sure we haven't fixed it since? The 'anyauth'
> magic has been written, rewritten and yet again rewritten (yes a third
> time). I believe the last version is the correct version as this was
> debated, discussed and tested a lot.

Sorry, yes, I guess I forgot to mention that I tested this using the
lastest CVS snapshot (which was 20050211 as of last night).

> If so, can you show us the --trace-ascii output of the failure? (edit
> out sensitive info before you post)

I've attached the trace-ascii file to this email. There is more than a 2
minute pause before the

>> Having tracked down the problem to this point I realize that I now
>> getting well out of league for looking at it on my own. Is this a
>> curl bug or an IIS bug?
>
> When this question arises it often is of no importance since people will
> want curl to work against IIS, even if it would do the wrong thing... In
> that light, it is always curl's problem to do right.

This windows machine is not available externally which means I cannot
easily give you access to it for testing. If you have an extra machine
that you can use for testing, Microsoft offers a free 6 month trial of
windows 2003 which can be downloaded from their site.

If that's not easy for you, I can do some remote debugging (feel free to
email me directly and let me know what info you need) and, of course, would
gladly test any patches that you come up with.