Re: Git Daemon Dummy: 301 Redirects for git:// to https://

From: Jeff King <peff@peff.net>
Date: Feb 23, 2016, 06:15 UTC
Message-ID: <20160223061517.GA3252@sigill.intra.peff.net>
In-Reply-To: <CAHmME9rTpGNHMKbXD48oBYm136=u79YiHjX5hm8ZYC4xSThJsA@mail.gmail.com>

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

Show 6 quoted lines

> 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