git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git over https and http 1.1

From
Peter Vereshagin <peter@vereshagin.org>
Date
May 19, 2011, 14:39 UTC
Message-ID
<20110519143934.GB5355@external.screwed.box>
In-Reply-To
<BLU0-SMTP195570CAA61AF8232B0295BC78F0@phx.gbl>

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

Previous: Daniel Stenberg
Message 3 of 3 in “git over https and http 1.1”
  1. Nir FriedmanMay 18, 2011
  2. Daniel StenbergMay 18, 2011
  3. Peter VereshaginMay 19, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.