From: Mark Wielaard <mark@klomp.org>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: overseers@sourceware.org
Subject: Re: git through http (or https)
Date: Wed, 04 Jan 2017 12:43:00 -0000 [thread overview]
Message-ID: <20170104124301.GL2187@stream> (raw)
In-Reply-To: <20170103234052.GD412@elastic.org>
On Tue, Jan 03, 2017 at 06:40:52PM -0500, Frank Ch. Eigler wrote:
> > http://sourceware.org/git/elfutils.git
> > The first two work, but the last one does a 304 redirect to https
> > but then gives a 403 forbidden.
>
> This is more or less working now. (We were missing the
> http-dumb-transport hooks/post-update).
Very nice. git clone and pull are now working on the http
(and https) URLs.
If the redirect to https is always on then maybe use
https://sourceware.org/git in gitweb_config.perl for
the git_base_url_list?
Also directly viewing https://sourceware.org/git/elfutils.git
still doesn't work because it gets redirected to the underlying
directory which is forbidden to view directly. If I read the
gitweb man page right then the rewrite rules in
htdocs/git/.htaccess would make that work. But they are
currently commented out. Could they be enabled?
That would make redirecting the old fedorahosted git URL
for elfutils work for all cases.
Thanks,
Mark
next prev parent reply other threads:[~2017-01-04 12:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 21:22 Mark Wielaard
2017-01-03 23:41 ` Frank Ch. Eigler
2017-01-04 12:43 ` Mark Wielaard [this message]
2017-01-05 16:03 ` Frank Ch. Eigler
2017-01-05 17:26 ` Mark Wielaard
2017-01-05 20:25 ` Frank Ch. Eigler
2017-01-08 23:31 ` Mark Wielaard
2017-01-08 23:33 ` Frank Ch. Eigler
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=20170104124301.GL2187@stream \
--to=mark@klomp.org \
--cc=fche@elastic.org \
--cc=overseers@sourceware.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).