From: Jürgen Kreileder <jk@blackdown.de>
Date: Mon, 28 Nov 2011 20:13:28 GMT
Subject: Re: gitweb: in-page errors don't work with mod_perl
Message-ID: <CAKD0Uuws=zU+Pg8afn91mm0t4Rp_GNF++dTYnjA9okndyR=cXQ@mail.gmail.com>
In-Reply-To: <201111281754.59205.jnareb@gmail.com>

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 header I set, e.g.
content-type.


Juergen