Jürgen Kreileder wrote: > On Mon, Nov 28, 2011 at 21:13, Jürgen Kreileder <jk@xxxxxxxxxxxx> wrote: > > On Mon, Nov 28, 2011 at 17:54, Jakub Narebski <jnareb@xxxxxxxxx> 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. I'm coming close to declaring that ModPerl::Registry is horribly broken with respect to error pages created by CGI, and say that we don't support it, removing mod_perl configuration examples from gitweb documentation. WTF 'return Apache2::Const::DONE;' doesn't work with ModPerl::Registry? It is supposed to work with native mod_perl scripts... -- Jakub Narebski Poland -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html