From: Marc Singer <elf@buici.com>
To: git@vger.kernel.org
Subject: gitweb testing with non-apache web server
Date: Thu, 3 Aug 2006 00:54:03 -0700 [thread overview]
Message-ID: <20060803075403.GA5238@buici.com> (raw)
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.
So, I wonder if someone who has a working gitweb would be willing to
test with Cherokee or some other resource conservative web server.
Cheers.
next reply other threads:[~2006-08-03 7:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 7:54 Marc Singer [this message]
2006-08-03 8:18 ` gitweb testing with non-apache web server 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
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=20060803075403.GA5238@buici.com \
--to=elf@buici.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.