{"thread":{"id":"27395","subject":"git over https and http 1.1","startedAt":"2011-05-18T12:46:18Z","lastAt":"2011-05-19T20:36:06Z","messageCount":3,"participants":["nir.friedman@greenhouse.lotus.com","Drew Northup","Daniel Stenberg"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"168133","messageId":"OF134A8B76.F0B9B9C0-ON85257894.00462851-85257894.00462862@greenhouse.lotus.com","threadId":"27395","inReplyTo":null,"subject":"git over https and http 1.1","fromName":"","fromEmail":"nir.friedman@greenhouse.lotus.com","sentAt":"2011-05-18T12:46:18Z","receivedAt":"2011-05-18T12:46:18Z","isPatch":false,"sender":{"key":"nir.friedman@greenhouse.lotus.com","avatar":null},"body":"I am using git with https as the transport protocol. \nResponse times were around 30 seconds before apache started processing the backend command. \nI added the flags -  BrowserMatch \"git\"      downgrade-1.0 force-response-1.0\n to the apache conf file, and response times were fast. \nThis seems to mean that the libcurl library is not dealing correctly with HTTP 1/1 over SSL. Is this the best fix? \nIf so, maybe appropriate documentation should be added to the git setup docs."},{"id":"168256","messageId":"1305837109.25259.11.camel@drew-northup.unet.maine.edu","threadId":"27395","inReplyTo":"OF134A8B76.F0B9B9C0-ON85257894.00462851-85257894.00462862@greenhouse.lotus.com","subject":"Re: git over https and http 1.1","fromName":"Drew Northup","fromEmail":"drew.northup@maine.edu","sentAt":"2011-05-19T20:31:49Z","receivedAt":"2011-05-19T20:31:49Z","isPatch":false,"sender":{"key":"drew.northup@maine.edu","avatar":"https://avatars.githubusercontent.com/u/18331571?v=4"},"body":"\nOn Wed, 2011-05-18 at 08:46 -0400, Nir.Friedman@greenhouse.lotus.com\nwrote:\n> I am using git with https as the transport protocol. \n> Response times were around 30 seconds before apache started processing the backend command. \n> I added the flags -  BrowserMatch \"git\"      downgrade-1.0 force-response-1.0\n>  to the apache conf file, and response times were fast. \n> This seems to mean that the libcurl library is not dealing correctly with HTTP 1/1 over SSL. Is this the best fix? \n> If so, maybe appropriate documentation should be added to the git setup docs.--\n\nSounds a little drastic to me... Perhaps to find out what's going on you\nmight set up a test repo behind an STunnel instance and have a look at\nthe TCP/HTTP stream between them? \n\nPerhaps Git+libcurl isn't using keep-alive? I'd have to check the code.\n\n-- \n-Drew Northup\n________________________________________________\n\"As opposed to vegetable or mineral error?\"\n-John Pescatore, SANS NewsBites Vol. 12 Num. 59\n"},{"id":"168257","messageId":"alpine.DEB.2.00.1105192235380.25633@tvnag.unkk.fr","threadId":"27395","inReplyTo":"1305837109.25259.11.camel@drew-northup.unet.maine.edu","subject":"Re: git over https and http 1.1","fromName":"Daniel Stenberg","fromEmail":"daniel@haxx.se","sentAt":"2011-05-19T20:36:06Z","receivedAt":"2011-05-19T20:36:06Z","isPatch":false,"sender":{"key":"daniel@haxx.se","avatar":"https://gravatar.com/avatar/69fdca87edd17cee21ca2e79fc2ff671d644603c3dc27167430f3cd3dbab7ba8?d=mp&s=160"},"body":"On Thu, 19 May 2011, Drew Northup wrote:\n\n> Perhaps Git+libcurl isn't using keep-alive? I'd have to check the code.\n\nThey do. HTTP 1.1 even does \"keep-alive\" by default...\n\n-- \n\n  / daniel.haxx.se\n"}]}