Daniel Stenberg wrote:
> >This seems to happen regardless of the FRESH_CONNECT and MAXCONNECTS
> >settings (i.e. I couldn't find values that make any difference).
>
> I guess you can try to pass on a "Connection: Keep-Alive" header.
>
> >Is there any way I can find out why libcurl is doing this?
>
> Only by reading source code. And the HTTP 1.0 specs of course.

By the way, some HTTPS servers respond with HTTP/1.0 and keep-alive
disabled to avoid Internet Explorer bugs. Notice this in the standard
Apache 2 config:

    SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown \
             downgrade-1.0 force-response-1.0

-- Jamie
Received on 2005-03-11