A further innocent question: I can understand the transfer proceeding
if there has not been any response within 1 second, but when the
remote end /does/ send an immediate ACK, why doesn't libcurl accept
the other side as HTTP 1.1 and immediately continue the transfer? Why
force the 1.0 behaviour on everyone, even on /known/ 1.1 servers?

On Sun, Sep 21, 2008 at 2:34 AM, Dan Fandrich <dan_at_coneharvesters.com> wrote:
> The 1 second timeout is hard-coded in libcurl. Since HTTP 1.0 servers don't
> support 100-continue, this is a fallback mechanism that allows a transfer
> to continue anyway.
-------------------------------------------------------------------
List admin: http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-users
FAQ: http://curl.haxx.se/docs/faq.html
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2008-09-21