From: Bernhard Voelker <mail@bernhard-voelker.de>
To: Simon Josefsson <simon@josefsson.org>, bug-gnulib@gnu.org
Subject: Re: [PATCH] Use https:// instead of git://.
Date: Sun, 10 Jan 2021 16:18:19 +0100 [thread overview]
Message-ID: <d3c27bd0-978c-4fc6-af67-a65f9395ab0f@bernhard-voelker.de> (raw)
In-Reply-To: <87sg79t24f.fsf@latte.josefsson.org>
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
next prev parent reply other threads:[~2021-01-10 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 0:09 [PATCH] Use https:// instead of git:// Simon Josefsson via Gnulib discussion list
2021-01-10 1:30 ` Bruno Haible
2021-01-10 10:34 ` Simon Josefsson via Gnulib discussion list
2021-01-10 12:20 ` Simon Josefsson via Gnulib discussion list
2021-01-10 15:18 ` Bernhard Voelker [this message]
2021-01-10 16:14 ` Bruno Haible
2021-01-10 19:22 ` Bernhard Voelker
2021-01-10 1:58 ` Jeffrey Walton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d3c27bd0-978c-4fc6-af67-a65f9395ab0f@bernhard-voelker.de \
--to=mail@bernhard-voelker.de \
--cc=bug-gnulib@gnu.org \
--cc=simon@josefsson.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).