From: Blu Corater <blu@daga.cl>
To: git@vger.kernel.org
Subject: Re: gitweb testing with non-apache web server
Date: Thu, 3 Aug 2006 15:21:52 -0400 [thread overview]
Message-ID: <20060803192152.GT7533@daga.cl> (raw)
In-Reply-To: <20060803162241.GB1287@buici.com>
On Thu, Aug 03, 2006 at 09:22:41AM -0700, Marc Singer wrote:
> On Thu, Aug 03, 2006 at 11:56:03AM -0400, Blu Corater wrote:
> > On Thu, Aug 03, 2006 at 12:54:03AM -0700, Marc Singer wrote:
> > > I would like to use gitweb with the Cherokee web server because the
> > > host that I have on hand has very limited RAM, 32MiB. Neither the
> > > version of gitweb available on Debian (v264) nor the latest in the git
> > > repo works.
> > >
> > > I did some debugging on the latest repo version. The lines
> > >
> > > our $project = ($cgi->param('p') || $ENV{'PATH_INFO'});
> > > if (defined $project) {
> > > ...
> > >
> > > are being executed even though the url is
> > >
> > > http://server/git
> > >
> > > I think that the problem is that Cherokee translates the request URL
> > > into
> > >
> > > http://server/git/
> > >
> > > which means that the $ENV{'PATH_INFO'} is the string "/" insted of
> > > being undefined.
> > >
> > > The error I'm seeing is that the request path is forbidden, but I
> > > suspect that this is some sort of misunderstanding between the web
> > > server and the script.
> >
> > I am using Cherokee+GitWeb and the behaviour observed is that
> > http://server/git will return the default Cherokee index page, but
> > http://server/git/, with a slash at the end, works.
>
> Will you share your Cherokee configuration script?
>
> The links look like this:
>
> http://scarlet/g?p=bsp.git;a=summary
>
> even when I start with
>
> http://scarlet/g
>
> or
>
> http://scarlet/g/
>
> So, I'm not sure I understand what you are saying.
Here is the interesting part of my cherokee.conf
------------------------------------------
UserDir public_html {
Directory / {
Handler common
}
Directory /scm/ {
Handler cgi {
ScriptAlias /home/blu/bin/gitweb.cgi
}
}
}
-----------------------------------------
So, I have the gitweb.cgi executable in a bin directory on my home and I
am telling Cherokee that when it sees the url http://server/~blu/scm/, it
should execute /home/blu/bin/gitweb.cgi
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.
Now, if I add
Directory /test/ {
Handler cgi
}
And copy gitweb.cgi to ~/public_html/test/, it seems there is no problem.
I can request http://server/~blu/test/gitweb.cgi or
http://server/~blu/test/gitweb.cgi/ and get the expected gitweb output.
It looks more like a Cherokee problem to me, but I don't have time to
investigate further right now.
--
Blu.
next prev parent reply other threads:[~2006-08-03 19:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 7:54 gitweb testing with non-apache web server Marc Singer
2006-08-03 8:18 ` Jakub Narebski
2006-08-03 15:34 ` Marc Singer
2006-08-03 15:48 ` Jakub Narebski
2006-08-03 16:20 ` Marc Singer
2006-08-03 18:21 ` Junio C Hamano
2006-08-03 18:37 ` Jakub Narebski
2006-08-03 19:41 ` Junio C Hamano
2006-08-03 20:14 ` Martin Waitz
2006-08-03 11:42 ` Sam Vilain
2006-08-03 15:56 ` Blu Corater
2006-08-03 16:22 ` Marc Singer
2006-08-03 19:21 ` Blu Corater [this message]
2006-08-03 20:27 ` Marc Singer
2006-08-03 23:55 ` Francis Daly
2006-08-04 6:11 ` Marc Singer
2006-08-04 19:48 ` Francis Daly
2006-08-04 7:30 ` Marc Singer
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=20060803192152.GT7533@daga.cl \
--to=blu@daga.cl \
--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).