Constantine Plotnikov <constantine.plotnikov@xxxxxxxxx> wrote: > On Thu, Jul 2, 2009 at 12:54 PM, Eric Wong<normalperson@xxxxxxxx> wrote: > > This doesn't work in the face of most HTTP-aware proxies[1], so it > > probably doesn't help those who have trouble accessing git:// servers in > > the first place... However, this could potentially be useful in places > > where a proxy providing CONNECT is not available. > > > The current lore is that to work with http proxies two separate > streams are needed, > one for input and one for outputs. > > This technique is described at > http://xmpp.org/extensions/xep-0124.html#technique > and other places. Actually, the problem with my approach here is that any HTTP proxies are free to rewrite chunked requests/responses to non-chunked ones (for compression, ssl, or even performance reasons). That and my approach requires both the client and server to be simutaneously sending and receiving responses in full-duplex channel which makes it impossible to work without chunking. IOW, there's no chance any HTTP proxy that dechunks or queues/coalesces chunked requests/responses can work with my approach. The big upside is that only one HTTP request is needed for a full clone, making this the most efficient way of using git over HTTP so far :) -- Eric Wong -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html