I think that in case of HTTP 1.0 the default shouldn't be persistant. I suppose it will fix the situation. Am I correct ?

You right, the "Proxy-Connection : close" header is not defined in the RFC, but it is used in a wild.

Roma

-----Original Message-----
From: Daniel Stenberg [mailto:daniel-curl_at_haxx.se]
Sent: Monday, August 30, 2004 10:52 AM
To: libcurl development
Subject: Re: HTTP 1.0 and multi handle question

On Mon, 30 Aug 2004, Roma Koifman wrote:

> Could it be because the default behavior from the http.c (line 1255 in
> 7.12.1 or line 1281 in 7.12.0) is
>
> /* We default to persistant connections */
> conn->bits.close = FALSE;
>
> and then in transfer.c we set it to TRUE only and only if the response
> was in HTTP 1.0.
>
> In my case the response is 1.1 and this is the reason for my problem ?

Yes, that's what causes libcurl to assume a persistent connection for this
case. I haven't actually considered this case before. I suppose it works
better for you if you make that assignment depend on the data->set.httpversion
value?

I'm also a bit puzzled about the "Proxy-Connection: close" header you
received. RFC2616 doesn't seem to mention such a header, but I would guess
that if libcurl would've understood it it would've closed that connection...

-- 
      Daniel Stenberg -- http://curl.haxx.se -- http://daniel.haxx.se
       Dedicated custom curl help for hire: http://haxx.se/curl.html
*****************************
Finjan Software
This e-mail and any attached files are confidential and may be legally
privileged. The unauthorized use, disclosure or copying of this email or
any information contained within it is strictly prohibited. This also
confirms that Finjan Software's Vital Security for E-Mail has scanned this
message for the presence of known viruses and potentially malicious
code.
Finjan Software - Prevention is the Best Cure!
*****************************