git over https and http 1.1

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.

-Nirf

On Wed, 18 May 2011, Nir Friedman wrote:

Can you please be a bit more elaborate on exactly what took that much time? What is a "response time" in this context?

How fast is "fast" compared to the previous 30 seconds?

I don't think that's what it means but I have to little data to go on. What libcurl version are you using on what platform?

You'll never silence the voice of the voiceless, Nir! 2011/05/18 15:30:18 +0300 Nir Friedman <nirfri@hotmail.com> => To git@vger.kernel.org : NF> I am using git with https as the transport protocol. NF> Response times were around 30 seconds before apache started processing the NF> backend command. NF> I added the flags [BrowserMatch "git" downgrade-1.0 NF> force-response-1.0] to the apache conf file, and response times were fast. NF> This seems to mean that the libcurl library is not dealing correctly with NF> HTTP 1/1 over SSL. Is this the best fix?

It's very unlikely for curl to work bad with https. Isn't it a DNS-related delay?

NF> If so, maybe appropriate documentation should be added to the git setup NF> docs.

73! Peter pgp: A0E26627 (4A42 6841 2871 5EA7 52AB 12F8 0CE1 4AAC A0E2 6627) -- http://vereshagin.org