certificate-based authentication for https hgwebdir clients

[Matt Mackall]

On Wed, 2009-01-07 at 11:05 +0100, Dirkjan Ochtman wrote:
> 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.

I'm sorry, is authenticating a client certificate not possible from
inside a CGI script?

-- 
Mathematics is the supreme nostalgia of our time.