git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: git@vger.kernel.org
Subject: Re: Git Daemon Dummy: 301 Redirects for git:// to https://
Date: Tue, 23 Feb 2016 01:15:17 -0500	[thread overview]
Message-ID: <20160223061517.GA3252@sigill.intra.peff.net> (raw)
In-Reply-To: <CAHmME9rTpGNHMKbXD48oBYm136=u79YiHjX5hm8ZYC4xSThJsA@mail.gmail.com>

On Tue, Feb 23, 2016 at 03:32:02AM +0100, Jason A. Donenfeld wrote:

> In case anyone else finds this useful, I wrote this:
> 
> https://git.zx2c4.com/git-daemon-dummy/about/
> 
> It's an epoll-based responder for git:// that simply returns an error
> telling users of a new URI.

Neat.

> The purpose is to phase out git-daemon in
> favor of more secure TLS/HTTPS endpoints. With HTTPS certificates now
> being free, seems like this could be useful.

Yeah, the existence of HTTPS (and the fact that the same URL can be both
anonymous and authenticated) is nice. Unfortunately, git-over-https is
not as efficient as the other protocols, because it's not asynchronously
bi-directional. It would probably be relatively simple to make a
"gits://" protocol, but I think it would be more interesting still if we
could do git-over-websockets, to get the ubiquity benefits of HTTP.

I looked into it once, but was unable to find any reasonably sized
explanation of how to implement either the server or client side of
websockets. :)

> My personal motivation is that I'd like to just totally kill the
> git-daemon service, but somebody hard coded a URI of mine into a real
> printed textbook [1], so I don't want it to go stale suddenly. So, I
> need some way of informing users of the new URI.

Darn printed books. I thought the Ministry of Truth was supposed to take
care of keeping our facts up to date.

-Peff

  reply	other threads:[~2016-02-23  6:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23  2:32 Git Daemon Dummy: 301 Redirects for git:// to https:// Jason A. Donenfeld
2016-02-23  6:15 ` Jeff King [this message]
2016-02-23 12:13   ` Duy Nguyen
2016-02-23 15:11   ` Jason A. Donenfeld
2016-02-23 15:11     ` Jason A. Donenfeld
2016-02-23 10:51 ` John Keeping
2016-02-23 15:10   ` Jason A. Donenfeld

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=20160223061517.GA3252@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=Jason@zx2c4.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;
as well as URLs for NNTP newsgroup(s).