I am using git with https as the transport protocol. Response times were around 30 seconds before apache started processing the backend command. I added the flags - BrowserMatch "git" downgrade-1.0 force-response-1.0 to the apache conf file, and response times were fast. This seems to mean that the libcurl library is not dealing correctly with HTTP 1/1 over SSL. Is this the best fix? If so, maybe appropriate documentation should be added to the git setup docs.
Drew NorthupRe: git over https and http 1.1
On Wed, 2011-05-18 at 08:46 -0400, Nir.Friedman@greenhouse.lotus.com wrote:
Show 6 quoted lines
> I am using git with https as the transport protocol. > Response times were around 30 seconds before apache started processing the backend command. > I added the flags - BrowserMatch "git" downgrade-1.0 force-response-1.0 > to the apache conf file, and response times were fast. > This seems to mean that the libcurl library is not dealing correctly with HTTP 1/1 over SSL. Is this the best fix? > If so, maybe appropriate documentation should be added to the git setup docs.--
Sounds a little drastic to me... Perhaps to find out what's going on you might set up a test repo behind an STunnel instance and have a look at the TCP/HTTP stream between them?
Perhaps Git+libcurl isn't using keep-alive? I'd have to check the code.
-- -Drew Northup ________________________________________________ "As opposed to vegetable or mineral error?" -John Pescatore, SANS NewsBites Vol. 12 Num. 59
Daniel StenbergRe: git over https and http 1.1
On Thu, 19 May 2011, Drew Northup wrote:
> Perhaps Git+libcurl isn't using keep-alive? I'd have to check the code.
They do. HTTP 1.1 even does "keep-alive" by default...
-- / daniel.haxx.se