From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: qemu.org server bandwidth report (May 2021)
Date: Mon, 10 May 2021 14:46:33 +0100 [thread overview]
Message-ID: <YJk5ObfemfPCI32J@redhat.com> (raw)
In-Reply-To: <CAJSP0QXMwSZqMRLXx3XYrrCe+OMP0k-hqFWb_GR_uMW35zZqDA@mail.gmail.com>
On Mon, May 10, 2021 at 02:40:16PM +0100, Stefan Hajnoczi wrote:
> On Mon, May 10, 2021 at 11:31 AM Daniel P. Berrangé <berrange@redhat.com> wrote:
> >
> > For the https:// URIs should we setup a HTTP redirect ?
> >
> > When git clones via https it fetches some specific paths which
> > I believe we have rules for in httpd conf:
> >
> > ScriptAliasMatch "^/git/(.*\.git/(HEAD|info/refs))$" \
> > /usr/libexec/git-core/git-http-backend/$1
> > ScriptAliasMatch "^/git/(.*\.git/git-(upload|receive)-pack)$" \
> > /usr/libexec/git-core/git-http-backend/$1
> >
> > If we set those URI path matches to send a HTTP 307 redirect
> > to gitlab, that would essentially kill off our git traffic on
> > qemu.org, while still allowing the qemu.org gitweb UI to
> > work normally. The downside is that people won't notice to
> > update their clone URIs. Still feels like an easy win and
> > we can easily remove the redirect if we use code 307.
>
> I remember there were concerns about warning messages that
> git-clone(1) prints when an HTTP redirect is encountered? If everyone
> is okay I can turn the git-http-backend(1) aliases into HTTP 307
> redirects to GitLab.
I presume that'll be the case with git fetch/pull too, and anything
else which talks to the server.
None the less, if git prints a warning message when getting a redirect,
I'd say that is probably a desirable feature, as it'll make it more
likely that people will fix their URIs to directly point at gitlab.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-05-10 13:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 9:49 qemu.org server bandwidth report (May 2021) Stefan Hajnoczi
2021-05-10 10:31 ` Daniel P. Berrangé
2021-05-10 13:40 ` Stefan Hajnoczi
2021-05-10 13:46 ` Daniel P. Berrangé [this message]
2021-05-10 15:47 ` Alex Bennée
2021-05-10 16:05 ` Stefan Hajnoczi
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=YJk5ObfemfPCI32J@redhat.com \
--to=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=thuth@redhat.com \
/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 NNTP newsgroup(s).