[PATCH v2 1/2] http: add option to enable 100 Continue responses

2013-10-11 Thread brian m. carlson
When using GSS-Negotiate authentication with libcurl, the authentication provided will change every time, and so the probe that git uses to determine if authentication is needed is not sufficient to guarantee that data can be sent. If the data fits entirely in http.postBuffer bytes, the data can

Re: [PATCH v2 1/2] http: add option to enable 100 Continue responses

2013-10-11 Thread Jonathan Nieder
brian m. carlson wrote: When using GSS-Negotiate authentication with libcurl, the authentication provided will change every time, and so the probe that git uses to determine if authentication is needed is not sufficient to guarantee that data can be sent. If the data fits entirely in

Re: [PATCH v2 1/2] http: add option to enable 100 Continue responses

2013-10-11 Thread brian m. carlson
On Fri, Oct 11, 2013 at 04:43:07PM -0700, Jonathan Nieder wrote: By default means when allowed to make its own choice, right? (i.e., the behavior git never gave libcurl a chance to try :)) Makes sense. Yes, at least according to Daniel Stenberg. I don't believe it is ever triggered the way