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-ASN: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 1665E1F8C6 for ; Wed, 8 Sep 2021 16:42:29 +0000 (UTC) From: Eric Wong To: meta@public-inbox.org Subject: [PATCH] git_http_backend: forward HTTP_GIT_PROTOCOL in request headers Date: Wed, 8 Sep 2021 14:42:29 -0200 Message-Id: <20210908164229.18537-1-e@80x24.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit List-Id: It looks like git-http-backend(1) will support HTTP_GIT_PROTOCOL, soon, and we won't have to add GIT_PROTOCOL support to support newer versions of the git protocol, either. Link: https://public-inbox.org/git/YTiXEEEs36NCEr9S@coredump.intra.peff.net/ --- lib/PublicInbox/GitHTTPBackend.pm | 1 + 1 file changed, 1 insertion(+) diff --git a/lib/PublicInbox/GitHTTPBackend.pm b/lib/PublicInbox/GitHTTPBackend.pm index c179ffef..b9a3e4f5 100644 --- a/lib/PublicInbox/GitHTTPBackend.pm +++ b/lib/PublicInbox/GitHTTPBackend.pm @@ -98,6 +98,7 @@ sub serve_smart { foreach my $name (qw(QUERY_STRING REMOTE_USER REMOTE_ADDR HTTP_CONTENT_ENCODING + HTTP_GIT_PROTOCOL CONTENT_TYPE SERVER_PROTOCOL REQUEST_METHOD)) {