Re: git:// protocol over SSL/TLS
- From
- Konstantin Khomoutov <flatworm@users.sourceforge.net>
- Date
- Dec 27, 2013, 14:56 UTC
- Message-ID
- <20131227185657.0dee9b2062fe6c632cd7d3a4@domain007.com>
- In-Reply-To
- <CAErtv25uWbsH15yohh+6Jun3eD51dZzvj7udoBf14_EwXzSUPg@mail.gmail.com>
On Fri, 27 Dec 2013 20:47:54 +0600 Sergey Sharybin <sergey.vfx@gmail.com> wrote:
[...]
Show 12 quoted lines
> > As discussed in an earlier thread here, a good indication of the > > dumb version of the protocol being in use is no display of the > > fetching progress on the client while doing `git clone` because this > > information (like "compressing objects ..." etc) is sent by the > > server-side Git process which is only there if HTTP[S] "was smart". > > Otherwise the client just GETs packs of objects, traverses them, > > GETs more and so on, so batches of HTTP GET requests correlating to > > clone sessions in the web server logs should also be indicative of > > the problem. > > Just to verify, if i see messages like "Receiving objects: 1% > (7289/705777), 1.72 MiB | 340.00 KiB/s" it means server is "smart" ?
I would say yes, because your Git knows the precise number of objects to receive. Unfortunately, I won't swear by this as this was a long time ago I have seen cloning using the dumb protocol.
By the way, here [1] is that discussion.
1. http://thread.gmane.org/gmane.comp.version-control.git/238933/focus=238946