Re: [PATCH] Disable dumb HTTP fallback with GIT_CURL_FALLBACK=0

2012-09-21 Thread Shawn Pearce
On Thu, Sep 20, 2012 at 10:26 PM, Jeff King wrote: > On Thu, Sep 20, 2012 at 04:05:03PM -0700, Shawn O. Pearce wrote: > >> But right now I am seeing failures in libcurl's SSL connection that >> may also be causing the smart connection failures. For example this >> trace, where libcurl was just not

Re: [PATCH] Disable dumb HTTP fallback with GIT_CURL_FALLBACK=0

2012-09-20 Thread Jeff King
On Thu, Sep 20, 2012 at 04:05:03PM -0700, Shawn O. Pearce wrote: > But right now I am seeing failures in libcurl's SSL connection that > may also be causing the smart connection failures. For example this > trace, where libcurl was just not able to connect to respond to the > 401 with a password.

Re: [PATCH] Disable dumb HTTP fallback with GIT_CURL_FALLBACK=0

2012-09-20 Thread Shawn Pearce
On Thu, Sep 20, 2012 at 10:24 AM, Jeff King wrote: > On Wed, Sep 19, 2012 at 10:57:35PM -0700, Shawn O. Pearce wrote: > >> > so transient errors on the initial smart >> > contact can cause us to fall back to dumb, >> >> Transient errors is actually what is leading me down this path. We see >> abou

Re: [PATCH] Disable dumb HTTP fallback with GIT_CURL_FALLBACK=0

2012-09-20 Thread Jeff King
On Wed, Sep 19, 2012 at 10:57:35PM -0700, Shawn O. Pearce wrote: > > I have been looking into this recently, as well. GitHub does not allow > > dumb http at all these days, > > Interesting that GitHub doesn't support dumb transfer either. Our objects are still in regular repos, and is served by

Re: [PATCH] Disable dumb HTTP fallback with GIT_CURL_FALLBACK=0

2012-09-19 Thread Shawn Pearce
On Wed, Sep 19, 2012 at 8:48 PM, Jeff King wrote: > On Wed, Sep 19, 2012 at 07:55:53PM -0700, Shawn O. Pearce wrote: > >> If the user doesn't want to use the dumb HTTP protocol, she may >> set GIT_CURL_FALLBACK=0 in the environment before invoking a Git >> protocol operation. This is mostly useful

Re* [PATCH] Disable dumb HTTP fallback with GIT_CURL_FALLBACK=0

2012-09-19 Thread Junio C Hamano
"Shawn O. Pearce" writes: > From: "Shawn O. Pearce" > > If the user doesn't want to use the dumb HTTP protocol, she may > set GIT_CURL_FALLBACK=0 in the environment before invoking a Git > protocol operation. This is mostly useful when testing against > servers that are known to not support the

Re: [PATCH] Disable dumb HTTP fallback with GIT_CURL_FALLBACK=0

2012-09-19 Thread Jeff King
On Wed, Sep 19, 2012 at 08:22:58PM -0700, Shawn O. Pearce wrote: > On Wed, Sep 19, 2012 at 7:55 PM, Shawn O. Pearce wrote: > > From: "Shawn O. Pearce" > > I can't explain why git send-email did this. I obviously didn't need > the extra From header here. format-patch didn't write it to the patch

Re: [PATCH] Disable dumb HTTP fallback with GIT_CURL_FALLBACK=0

2012-09-19 Thread Jeff King
On Wed, Sep 19, 2012 at 07:55:53PM -0700, Shawn O. Pearce wrote: > From: "Shawn O. Pearce" > > If the user doesn't want to use the dumb HTTP protocol, she may > set GIT_CURL_FALLBACK=0 in the environment before invoking a Git > protocol operation. This is mostly useful when testing against > ser

Re: [PATCH] Disable dumb HTTP fallback with GIT_CURL_FALLBACK=0

2012-09-19 Thread Shawn Pearce
On Wed, Sep 19, 2012 at 7:55 PM, Shawn O. Pearce wrote: > From: "Shawn O. Pearce" I can't explain why git send-email did this. I obviously didn't need the extra From header here. format-patch didn't write it to the patch file, it was injected by send-email. My .git/config is pretty simple, the n

[PATCH] Disable dumb HTTP fallback with GIT_CURL_FALLBACK=0

2012-09-19 Thread Shawn O. Pearce
From: "Shawn O. Pearce" If the user doesn't want to use the dumb HTTP protocol, she may set GIT_CURL_FALLBACK=0 in the environment before invoking a Git protocol operation. This is mostly useful when testing against servers that are known to not support the dumb protocol. If the smart service det