Hi, On Wed, Dec 2, 2009 at 2:18 AM, Daniel Stenberg <daniel@xxxxxxx> wrote: > If '#@!*@!*' is your pattern for matching libcurl or curl, then sure libcurl > certainly has no problem at all to send as many requests you like > back-to-back. I have a feeling Shawn's referring to the git http library on top of that. ;) > The rewinding business is only really necessary for multipass authentication > when Expect: 100-continue doesn't work (and thus libcurl has started to send > data that the server will discard and thus is needed to get sent again). And > that's not something you can blame "the #@!*@!* library" for, but rather > your server end and/or how HTTP is defined to work. According to Martin, Expect: 100-continue is not working due to libcurl. I quote him: Date: Tue, 1 Dec 2009 12:28:26 +0200 (EET) Subject: Re: [PATCH 0/2] http: allow multi-pass authentication On Tue, Dec 1, 2009 at 6:28 PM, Martin Storsjö <martin@xxxxxxxxx> wrote: > Normally, libcurl should add the Expect: 100-continue header > automatically, but for some reason > (http://article.gmane.org/gmane.comp.web.curl.library/25992) it doesn't, > so that's probably why we're manually adding that header in > remote-curl.c:371 at the moment. libcurl doesn't detect this at the moment > (http://article.gmane.org/gmane.comp.web.curl.library/25991) so it won't > wait for the 100 continue response before starting to send the body data. But, again, don't read my blaming of libcurl for this 100 business as a criticism of curl. -- Cheers, Ray Chuan -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html