From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Gaeseric Vandal <gaiseric.vandal@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Updates on centos7 break git access via git-http-backend
Date: Sun, 18 Aug 2019 17:00:49 +0000 [thread overview]
Message-ID: <20190818170032.GF365197@genre.crustytoothpaste.net> (raw)
In-Reply-To: <009f01d555cc$50564ca0$f102e5e0$@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2117 bytes --]
On 2019-08-18 at 13:53:28, Gaeseric Vandal wrote:
>
> This a is a clarification of an earlier post. I thought gitweb was the problem.
>
>
> The actual problem appears to be with /usr/libexec/git-core/git-http-backend.
>
> Gitweb provides a list to unauthenticated users of available repositories. I don't need that function so I have removed that package to avoid unexpected conflicts.
>
> I recently applied the latest patches on centos7, including git-1.8.3.1-20. When I try to access git repos (either via web browser or git command line.) Repos are configured to require LDAP authentication.
>
> The httpd ssl-error.log shows
> #
> [Sun Aug 18 09:22:48.113435 2019] [authz_core:debug] [pid 30167] mod_authz_core.c(809): [client x.x.x.x:35876] AH01626: authorization result of <RequireAny>: granted [Sun Aug 18 09:22:48.119012 2019] [cgi:error] [pid 30167] [client x.x.x.x:x] AH01215: Request not supported: '/export/gitrepos/ABC [Sun Aug 18 09:22:48.119069 2019] [headers:debug] [pid 30167] mod_headers.c(823): AH01502: headers: ap_headers_output_filter() [Sun Aug 18 09:22:53.124599 2019] [ssl:info] [pid 30167] (70007)The timeout specified has expired: [client x.x.x.x:35876] AH01991: SSL input filter read failed.
> [Sun Aug 18 09:22:53.124723 2019] [ssl:debug] [pid 30167] ssl_engine_io.c(993): [client x.x.x.x:35876] AH02001: Connection closed to child 1 with standard shutdown (#
>
If this only breaks on upgrade from an older version of Git on CentOS,
I'd file a bug with the CentOS (or Red Hat) folks. I expect that this
is due to a patch that Red Hat applied, and not really a limitation in
Git.
As you might be aware, Git 1.8.3.1 is rather old; we've just released
2.23.0. You could try using a version of Git from Software Collections
(2.18 is available) and see if that works better for you, but I suspect
most folks on the list don't pay much attention to versions before 2.0.
Be aware that it may be Apache that's the problem here and not Git if it
was also upgraded.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]
prev parent reply other threads:[~2019-08-18 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <009e01d555cb$6c8ed640$45ac82c0$@gmail.com>
2019-08-18 13:53 ` Updates on centos7 break git access via git-http-backend Gaeseric Vandal
2019-08-18 17:00 ` brian m. carlson [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190818170032.GF365197@genre.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=gaiseric.vandal@gmail.com \
--cc=git@vger.kernel.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