Hello,

I did a patch for this BUG - and for me, it seems to run.
Sorry, but I had to introduce a new ErrorCode - that is only used
internally. I can also define a flag in one of the structures to transport
the needed information between the calls.

I tried not to change to much. Would you please have a look on the changed
files (attached) if you see any problems. I am open for all comments.

Olaf

Am Thu, 26 Oct 2006 22:24:35 +0200 hat Daniel Stenberg <daniel_at_haxx.se>
geschrieben:

> On Thu, 26 Oct 2006, Source wrote:
>
>> When using the Jana-Server2 with authentication to access a
>> https-Server,
>> the JANA-Server sends a Connection-Close on first access without
>> password.
>> Curl sends the second request with the password on the same handle
>> which is
>> then not accepted by the Jana-server.
>
> Welcome to KNOWN_BUGS #25. This has been a very popular bug to report
> lately.
>
> Yes, unfortunately libcurl doesn't properly deal with a CONNECT response
> that
> is closed, as it assumes it will always remain alive if the connection is
> good.
>
> I'll happily accept patches that improve this situation. I have no
> personal
> plans to attack this problem right now, and I don't know anyone working
> on it.
>