Re: gitweb: in-page errors don't work with mod_perl
- From
Jürgen Kreileder <jk@blackdown.de>
- Date
- Nov 28, 2011, 21:42 UTC
- Message-ID
- <CAKD0UuzsV7A_j8YD4b0Lb95L2NcRcSu5PH8C9aZQmEx3tOuQjQ@mail.gmail.com>
- In-Reply-To
- <CAKD0Uuws=zU+Pg8afn91mm0t4Rp_GNF++dTYnjA9okndyR=cXQ@mail.gmail.com>
On Mon, Nov 28, 2011 at 21:13, Jürgen Kreileder <jk@blackdown.de> wrote:
Show 16 quoted lines
> On Mon, Nov 28, 2011 at 17:54, Jakub Narebski <jnareb@gmail.com> wrote: > [...] >> >> The configuration is very similar. Perhaps that is the difference between >> Apache 2.0.x (mine) and Apache 2.2.x (yours). >> >> Does adding `$r->err_headers_out();` before `$r->status(200);` helps? >> I'm grasping at straws here. mod_perl documentation is not very helpful. > > Doesn't help unfortunately. It's hard to find any information about > this on the net (except for your comment on stackoverflow :). > > The only way to get mod_perl to return a custom error message with > correct status code I've found so far is $r->custom_response($status, > $msg). Unfortunately mod_perl then ignores headers I set, e.g. > content-type.
I guess this explains it: http://foertsch.name/ModPerl-Tricks/custom-content_type-with-custom_response.shtml Requires quite some restructuring to gitweb.perl.
Juergen