On Wed, 2011-05-18 at 08:46 -0400, Nir.Friedman@xxxxxxxxxxxxxxxxxxxx wrote: > 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 -- 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