Re: [PATCH] Use https:// instead of git://.

[Bernhard Voelker]

On 1/10/21 1:20 PM, Simon Josefsson via Gnulib discussion list wrote:
> Using https:// instead of git:// makes this slightly better.

Both https:// and git:// URLs are configured to be read-only on the
Savannah server, and only the ssh:// variant allows pushing.

https://git-scm.com/book/en/v2/Git-Internals-Transfer-Protocols
https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols

For HTTP/HTTPS, the question is if the server is configured for
"smart HTTP" or if the client has to fall back to "dumb HTTP".
The latter would come with slower performance and more round-trips.
The Savannah admins should have an answer to that question.

The git:// protocol is definitely always using the "smart" way,
but - as you said - doesn't allow authentication.  Well, http://
is probably not configured to do that either, and we probably
don't need that for the read-only variant.
The disadvantage of the git:// protocol is that it needs port 9418,
and therefore some corporate networks may have some problems.

Unless we have proof from the Savannah admins that https:// is setup
to be "smart" (whatever that involves), I'd therefore prefer the
always-"smart" git://.

Have a nice day,
Berny