All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nir.Friedman@greenhouse.lotus.com
To: git@vger.kernel.org
Subject: git over https and http 1.1
Date: Wed, 18 May 2011 08:46:18 -0400	[thread overview]
Message-ID: <OF134A8B76.F0B9B9C0-ON85257894.00462851-85257894.00462862@greenhouse.lotus.com> (raw)
In-Reply-To: 

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.

             reply	other threads:[~2011-05-18 12:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18 12:46 Nir.Friedman [this message]
2011-05-19 20:31 ` git over https and http 1.1 Drew Northup
2011-05-19 20:36   ` Daniel Stenberg
  -- strict thread matches above, loose matches on Subject: below --
2011-05-18 12:30 Nir Friedman
2011-05-18 12:41 ` Daniel Stenberg
2011-05-19 14:39 ` Peter Vereshagin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=OF134A8B76.F0B9B9C0-ON85257894.00462851-85257894.00462862@greenhouse.lotus.com \
    --to=nir.friedman@greenhouse.lotus.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.