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

git over https and http 1.1

From
Nnir.friedman@greenhouse.lotus.com <nir.friedman@greenhouse.lotus.com>
Date
May 18, 2011, 12:46 UTC
Message-ID
<OF134A8B76.F0B9B9C0-ON85257894.00462851-85257894.00462862@greenhouse.lotus.com>
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.
Next: Drew Northup
Message 1 of 3 in “git over https and http 1.1”
  1. nir.friedman@greenhouse.lotus.comMay 18, 2011
  2. Drew NorthupMay 19, 2011
  3. Daniel StenbergMay 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.