certificate-based authentication for https hgwebdir clients

Dirkjan Ochtman dirkjan at ochtman.nl
Wed Jan 7 10:05:29 UTC 2009


On Wed, Jan 7, 2009 at 01:23, Matt Mackall <mpm at selenic.com> wrote:
> And I'm saying that's not allowed. Every feature of 'hg serve' needs to
> be in hgweb because *hgweb* is the full-featured solution. If we have
> feature A only in one and feature B only in the other, people who want A
> and B together will be out of luck. (and hgweb here really means hgweb
> +hgwebdir)

I'm not really sure that's right. If not using hg serve, hgweb(dir) is
served from behind a real web server (e.g. Apache), whether it be
through mod_wsgi, CGI or FCGI. So, for the server part, at least, I
think we only have to support hg serve, but not generic hgweb(dir).
BUT, if that's true, it probably shouldn't touch hgweb(dir) code,
either.

It seems this patch mixes client-side and server-side support, it
would be useful to split those out into different patches. It would
also be useful if any new version of the patch was submitted as an
inline patch using the normal patchbomb trickery.

Cheers,

Dirkjan


More information about the Mercurial-devel mailing list