# git over https and http 1.1 3 messages from 2011-05-18 to 2011-05-19. Participants: Nir Friedman, Daniel Stenberg, Peter Vereshagin. Thread: https://gitlist.dev/t/27394 ## Nir Friedman, 2011-05-18 12:30 Subject: git over https and http 1.1 Message-ID: URL: https://gitlist.dev/e/BLU0-SMTP195570CAA61AF8232B0295BC78F0%40phx.gbl ``` 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 ``` ## Daniel Stenberg, 2011-05-18 12:41 Subject: Re: git over https and http 1.1 Message-ID: URL: https://gitlist.dev/e/alpine.DEB.2.00.1105181437510.3057%40tvnag.unkk.fr In-Reply-To: ``` On Wed, 18 May 2011, Nir Friedman wrote: > I am using git with https as the transport protocol. Response times were > around 30 seconds before apache started processing the backend command. Can you please be a bit more elaborate on exactly what took that much time? What is a "response time" in this context? > I added the flags [BrowserMatch "git" downgrade-1.0 > force-response-1.0] to the apache conf file, and response times were fast. How fast is "fast" compared to the previous 30 seconds? > This seems to mean that the libcurl library is not dealing correctly with > HTTP 1/1 over SSL. 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? -- / daniel.haxx.se ``` ## Peter Vereshagin, 2011-05-19 14:39 Subject: Re: git over https and http 1.1 Message-ID: <20110519143934.GB5355@external.screwed.box> URL: https://gitlist.dev/e/20110519143934.GB5355%40external.screwed.box In-Reply-To: ``` You'll never silence the voice of the voiceless, Nir! 2011/05/18 15:30:18 +0300 Nir Friedman => 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 ```