From: Francis Daly <francis@daoine.org>
Date: Thu, 03 Aug 2006 23:55:36 GMT
Subject: Re: gitweb testing with non-apache web server
Message-ID: <20060803235536.GJ17966@craic.sysops.org>
In-Reply-To: <20060803202703.GA13147@buici.com>

> Marc Singer wrote: 
> On Thu, Aug 03, 2006 at 03:21:52PM -0400, Blu Corater wrote:

Hi there,

> > If I request http://server/~blu/scm, Cherokee returns Cherokee's default
> > index page. Only if I request http://server/~blu/scm/, Cherokee returns
> > the expected output from gitweb.

This is due to one apparent bug in Cherokee's Directory handling.

> I can see the project overview page, but all of the links bring me
> back to the same top-level page, no summary, not logs.  I've verified
> that the web server's user can read the git repo. 

And this is due a a different, but arguably related, one.  (The 301
handler ignores things it shouldn't.)

> I don't doubt that this is a cherokee issue.

Cherokee's handling of both Directory and Request sections with cgi and
Scriptalias seems a bit funky (in different ways).  If you want to use
Cherokee configured this way, you may find it handy to add

$my_uri .= '/';

to your version of gitweb.cgi shortly after it is set -- that should
break most of the generated links in a way that causes them to work with
this server.

$my_url is only used in a few places, but it may be worth doing the same
thing to it too.

Or use a web server which isn't broken in this particular way.

Good luck,

	f
-- 
Francis Daly        francis@daoine.org