On Tue, 8 May 2007, Luigi Grilli wrote:

> I forgot to mention that Firefox can handle correctly this situation. And
> also the proxy(squid) itself.

I know, others have mentioned this as well but without suggested heuristics on
how we want libcurl to behave that's not much help to know that other
softwares deal with it differently.

> If the default behaviour is to consider the server persistent why not have a
> option (like --close) to let the curl/libcurl user decide the default. So
> having this option will send the "Connection: close" header and will expect
> the server to close the connection (even if it doesn't send the same header)
> so the library will receive the body until the server closes the connection.

Yes, sure, we could have an option that for this case when there's no headers
it would assume a "Connection: close" header.

Personally, I'm off for a week's vacation now so nothing more will happen from
me for a while. This should be fairly easy for someone else to add an option
and patch for though.

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