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

2013-10-11 Thread Shawn Pearce
On Fri, Oct 11, 2013 at 3:31 PM, brian m. carlson wrote: > On Thu, Oct 10, 2013 at 01:14:28AM -0700, Shawn Pearce wrote: >> Even if you want to live in the fairy land where all servers support >> 100-continue, I'm not sure clients should pay that 100-160ms latency >> penalty during ancestor negoti

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

2013-10-11 Thread brian m. carlson
On Thu, Oct 10, 2013 at 01:14:28AM -0700, Shawn Pearce wrote: > If a large enough percentage of users are stuck behind a proxy that > doesn't support 100-continue, it is hard to rely on that part of HTTP > 1.1. You need to build the work-around for them anyway, so you might > as well just make ever

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

2013-10-10 Thread Shawn Pearce
On Wed, Oct 9, 2013 at 6:35 PM, brian m. carlson wrote: > On Wed, Oct 09, 2013 at 05:37:42PM -0400, Jeff King wrote: >> On Wed, Oct 09, 2013 at 02:19:36PM -0700, Shawn O. Pearce wrote: >> > 206b099 was written because the Google web servers for >> > android.googlesource.com and code.google.com do

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

2013-10-09 Thread Jeff King
On Thu, Oct 10, 2013 at 01:35:47AM +, brian m. carlson wrote: > > I don't have a GSS-enabled server to test on. Brian, can you try the > > patch at the end of this message on your non-working server and see what > > it outputs? > > It doesn't trigger. My server only requires authentication f

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

2013-10-09 Thread brian m. carlson
On Wed, Oct 09, 2013 at 05:37:42PM -0400, Jeff King wrote: > On Wed, Oct 09, 2013 at 02:19:36PM -0700, Shawn O. Pearce wrote: > > 206b099 was written because the Google web servers for > > android.googlesource.com and code.google.com do not support > > 100-continue semantics. This caused the client

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

2013-10-09 Thread Jeff King
On Wed, Oct 09, 2013 at 02:19:36PM -0700, Shawn O. Pearce wrote: > > I'd be more comfortable defaulting this to "on" if I understood more > > about the original problem that led to 959dfcf and 206b099. It sounds > > like enabling this all the time will cause annoying stalls in the > > protocol, un

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

2013-10-09 Thread Shawn Pearce
On Wed, Oct 9, 2013 at 12:30 PM, Jeff King wrote: > On Tue, Oct 08, 2013 at 08:48:06PM +, 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 >> authenticati

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

2013-10-09 Thread Jeff King
On Tue, Oct 08, 2013 at 08:48:06PM +, 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