From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-Status: No, score=-3.9 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS, SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 788081F4B4 for ; Sun, 10 Jan 2021 15:18:29 +0000 (UTC) Received: from localhost ([::1]:35662 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kycU8-0007Px-13 for normalperson@yhbt.net; Sun, 10 Jan 2021 10:18:28 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:46374) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kycU5-0007Pr-UD for bug-gnulib@gnu.org; Sun, 10 Jan 2021 10:18:25 -0500 Received: from mout.kundenserver.de ([217.72.192.73]:47747) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kycU4-0001fB-5D for bug-gnulib@gnu.org; Sun, 10 Jan 2021 10:18:25 -0500 Received: from [192.168.101.10] ([91.12.160.30]) by mrelayeu.kundenserver.de (mreue106 [212.227.15.183]) with ESMTPSA (Nemesis) id 1N2EDg-1jxbj03YMg-013bSh; Sun, 10 Jan 2021 16:18:20 +0100 Subject: Re: [PATCH] Use https:// instead of git://. To: Simon Josefsson , bug-gnulib@gnu.org References: <878s91vei4.fsf@latte.josefsson.org> <11756592.SzArdBrhr3@omega> <87wnwlt715.fsf@latte.josefsson.org> <87sg79t24f.fsf@latte.josefsson.org> From: Bernhard Voelker Message-ID: Date: Sun, 10 Jan 2021 16:18:19 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: <87sg79t24f.fsf@latte.josefsson.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:Vv4xya8ylAuliYWzgPDy0xm5gELrXrKuw6N2MEWSNxKWdmpXJIT 7c+5PYNdpcJL43NrK4Ey8uSY5RBGmzrnH1vFxY9hdeeI7L2VZEFyhHQoVqZa5coFtiQ3qac dXQKDQppbC0euf9KzgDt08MoWhP4e/ZwV9tQcECbwTos9tULE1fFDwNnaXk1WhAmPt9S/h4 yKsMYjmb+2As1XqQ0J3BA== X-UI-Out-Filterresults: notjunk:1;V03:K0:ovzsLe/ekDE=:3aNcXKZ8uuBstw860ebfrK A1KgAzrTAZizOuKVK/jfyiUiHzfOOhSEEWHwmFPbDDH1jVsM3Hy1KXPQTbnYh54n6QMHXI+TV BlOznlsy4YfVr8wyEWW8Humx1llV0XuXX/prqBLetD9OXCyeRyfCwodK5L9k5/QpHvlYA5aJD AfjfkEUnPXAZmAIhK90zQjvRwbLYCwQR5ax3ZF7gPFmLt+8D3ikjbZUZRYTYXpzuPmYnJOfl1 bJ7vI2w07yevNr5g6hMv9k2RGLA+rg8XfkDvZLrvQB0/YyTqTtKrVZsDA3J0TMwWk45+4A/lu lQgpbbQkdowMhNRqmu5f3VQ7+7ofYXeQtbS7vzm6o5cgIUD/sUgyCRV5EzUUlLbswEBkMDPf8 iJ4YvLY0tEbyjxYPmqa9zN+055gDxgc/M6SpF9/hC3/syHvqGd018VAStjgWbiRenwZeC7y2P nwUYRE25/w== Received-SPF: none client-ip=217.72.192.73; envelope-from=mail@bernhard-voelker.de; helo=mout.kundenserver.de X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, NICE_REPLY_A=-0.012, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_NONE=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: bug-gnulib@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Gnulib discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnulib-bounces+normalperson=yhbt.net@gnu.org Sender: "bug-gnulib" 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