From: Jakub Narebski <jnareb@gmail.com>
To: julio.lajara@alum.rpi.edu
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Anders Kaseorg" <andersk@mit.edu>,
"Jonathan Nieder" <jrnieder@gmail.com>,
git@vger.kernel.org,
"Pavan Kumar Sunkara" <pavan.sss1991@gmail.com>
Subject: Re: Potential bug in gitweb 1.7.2
Date: Mon, 26 Jul 2010 16:23:04 +0200 [thread overview]
Message-ID: <201007261623.05850.jnareb@gmail.com> (raw)
In-Reply-To: <4C4D932A.1010101@gmail.com>
On Mon, 26 Jul 2010, Julio Lajara wrote:
> Hi, Ive managed to narrow down the issue to a line in the gitolite's
> contrib/gitweb/gitweb.conf that I appended to the default
> /etc/gitweb.conf . It was working with 1.7.0.4 but 1.7.2 doesnt like
> this line:
>
> $ENV{GL_USER} = $cgi->remote_user || "gitweb";
>
> I corrected it by just setting it equal to gitweb and all is well now.
I think the following commit is the reason that this stopped working
869d588 (gitweb: Move evaluate_gitweb_config out of run_request, 2010-07-05)
>From its commit message:
gitweb: Move evaluate_gitweb_config out of run_request
Move evaluate_gitweb_config() and evaluate_git_version() out of
run_request() to run(), making them not run one for each request.
This changes how git behaves in FastCGI case.
This change makes it impossible to have config which changes with
request, but I don't think anyone relied on such (hidden action)
behavior.
I guess I was wrong about that. I wonder if it would be possible to
re-enable this feature (which I think is needed to be able to use
$cgi->remote_user) but without having all pay the [slight] performance
penalty of including (and I think parsing) config file once per each
request.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2010-07-26 14:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 4:55 Potential bug in gitweb 1.7.2 Julio Lajara
2010-07-26 5:08 ` Jonathan Nieder
2010-07-26 9:27 ` Anders Kaseorg
2010-07-26 13:10 ` Julio Lajara
2010-07-26 13:36 ` Jakub Narebski
2010-07-26 13:39 ` Ævar Arnfjörð Bjarmason
2010-07-26 13:52 ` Julio Lajara
2010-07-26 14:23 ` Jakub Narebski [this message]
2010-07-31 3:01 ` [PATCH/RFC] gitweb: allow configurations that change with each request Jonathan Nieder
2010-08-02 19:35 ` Jakub Narebski
2010-08-02 21:01 ` Jonathan Nieder
2010-08-02 21:25 ` Jakub Narebski
2010-07-26 15:23 ` Potential bug in gitweb 1.7.2 Jonathan Nieder
2010-07-26 18:50 ` Anders Kaseorg
2010-07-27 0:09 ` Jonathan Nieder
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=201007261623.05850.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=andersk@mit.edu \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=julio.lajara@alum.rpi.edu \
--cc=pavan.sss1991@gmail.com \
/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).