On Tue, 18 Feb 2014, Jeff King wrote:
I think there is still an unrelated issue with curl_multi preventing
connection reuse, but I'm not sure from what you say below...
I'm not clear whether you mean by this that it is _expected_ in my test
program for curl not to reuse the connection. Or
On Tue, 18 Feb 2014, Jeff King wrote:
I'm not clear whether you mean by this that it is _expected_ in my test
program for curl not to reuse the connection. Or that curl may simply have
to do a little more work, and it is still a bug that the connection is not
reused.
Okey, I checked this
On Sun, Feb 16, 2014 at 02:33:06PM +0100, Daniel Stenberg wrote:
On Sun, 16 Feb 2014, Daniel Stenberg wrote:
Right, the problem is there to make sure that a NTLM-auth
connection with different credentials aren't re-used. NTLM with its
connection-oriented authentication breaks the
On Sun, Feb 16, 2014 at 01:18:52PM +0100, Daniel Stenberg wrote:
On Sat, 15 Feb 2014, Kyle J. McKay wrote:
If pipelining is off (the default) and total connections is not 1
it sounds to me from the description above that the requests will
be executed on separate connections until the
On Mon, 17 Feb 2014, Jeff King wrote:
Right; I'd expect multiple connections for parallel requests, but in this
case we are completing the first and removing the handle before starting the
second. Digging further, I was able to reproduce the behavior with a simple
program:
Yeah, given your
On Tue, Feb 18, 2014 at 08:13:16AM +0100, Daniel Stenberg wrote:
Right; I'd expect multiple connections for parallel requests, but
in this case we are completing the first and removing the handle
before starting the second. Digging further, I was able to
reproduce the behavior with a simple
On Sat, 15 Feb 2014, Kyle J. McKay wrote:
If pipelining is off (the default) and total connections is not 1 it sounds
to me from the description above that the requests will be executed on
separate connections until the maximum number of connections is in use and
then there might be some
On Sun, 16 Feb 2014, Daniel Stenberg wrote:
Right, the problem is there to make sure that a NTLM-auth connection with
different credentials aren't re-used. NTLM with its connection-oriented
authentication breaks the traditional HTTP paradigms and before this change
there was a risk that
I've noticed that git does not reuse http connections when fetching, and
I'm trying to figure out why. It seems related to our use of two curl
features:
1. If we use the curl_multi interface (even though we are doing the
requests sequentially), we do not get reuse.
2. If we set
On Feb 15, 2014, at 20:05, Jeff King wrote:
I've noticed that git does not reuse http connections when fetching,
and
I'm trying to figure out why. It seems related to our use of two curl
features:
1. If we use the curl_multi interface (even though we are doing the
requests sequentially),
10 matches
Mail list logo
