From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: Jeff Cody <jcody@redhat.com>
Subject: [Qemu-devel] https:// for GIT submodules / "smart" HTTP protocol on git.qemu.git
Date: Mon, 19 Mar 2018 16:49:39 +0000 [thread overview]
Message-ID: <20180319164939.GA3151@redhat.com> (raw)
Most of QEMU regular developers are fortunate to have unfiltered internet
access which allows using the git:// protocol. People working in more
old fashioned / paranoid environments often find access to anything other
than http(s) blocked by firewalls. They'll get a bad experiance when trying
to build QEMU, when we try to initialize the git submodules and git://
protocol fails to connect.
We could improve life for people behind such nasty firewalls if we made our
GIT submodules use https:// URIs, instead of git:// URIs. There is one snag.
Historically git:// URIs were strongly preferred over http(s):// URIs for
reasons for performance. Modern GIT though, supports both the traditional
"dumb" HTTP protocol (which is horribly slow) and a modern "smart" HTTP
protocol whose performance matches that of git:/// URIs.
Unfortunately it seems that git.qemu.org is not configured to enable the
smart HTTP protocol.
So can we get a todo item for git.qemu.org get the web server setup to
enable the smart GIT protocol, so we can then enable use of http:// by
default for all the submodules to improve life for contributors.
FYI, you can validate if a server supports the smart protocol or not
by querying $REPO_URI/info/refs?service=git-upload-pack and seeing
if the response includes a header
Content-Type: application/x-git-upload-pack-advertisement
qemu.org does not:
$ wget -S 'https://git.qemu.org/git/qemu.git/info/refs?service=git-upload-pack' 2>&1 | grep Content-Type
and shows terrible git clone performance for http:// uris
but github for example does
$ wget -S 'https://github.com/qemu/qemu.git/info/refs?service=git-upload-pack' 2>&1 | grep Content-Type
Content-Type: application/x-git-upload-pack-advertisement
and shows great performance for http:// URIs
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 reply other threads:[~2018-03-19 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 16:49 Daniel P. Berrangé [this message]
2018-03-19 18:28 ` [Qemu-devel] https:// for GIT submodules / "smart" HTTP protocol on git.qemu.git Daniel P. Berrangé
2018-03-19 19:10 ` Jeff Cody
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=20180319164939.GA3151@redhat.com \
--to=berrange@redhat.com \
--cc=jcody@redhat.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.