Perrin Harkins wrote:
On Fri, Apr 25, 2008 at 12:18 AM, Perl Junkie <[EMAIL PROTECTED]> wrote:
PerlOptions ParseHeaders
I think that should be +ParseHeaders. See
http://perl.apache.org/docs/2.0/user/porting/compat.html#C_PerlSendHeader_
I did finally see that in another sec
On Thu, Apr 24, 2008 at 4:16 PM, Mark Stosberg <[EMAIL PROTECTED]> wrote:
> No, I'm not. Are there debugging techniques that help me confirm
> this?
Sorry Mark, I misread your mail. I thought you were using PerlSetVar.
What are you doing exactly? PerlSetEnv PERL5LIB?
- Perrin
On Fri, Apr 25, 2008 at 12:18 AM, Perl Junkie <[EMAIL PROTECTED]> wrote:
> PerlOptions ParseHeaders
I think that should be +ParseHeaders. See
http://perl.apache.org/docs/2.0/user/porting/compat.html#C_PerlSendHeader_
> (2) It took me a while to figure out that Apache::Registry has becom
Okay, it's been a while, despite the name, that I've done any serious
playing around with MP. Since 1.0. I've just installed and gotten
running MP 2.0 on Apache 2.2.8... I'm doing the "ground up" and trying
to get registry scripts working first and I've run into the following,
right-off-the-
On Apr 24, 2008, at 02:20, Torsten Foertsch wrote:
Well, I think I can shed some light on that mystery. When you use
the "perl-script" handler instead of "modperl" then your C-level
response
handler is modperl_response_handler_cgi (see src/modules/perl/
mod_perl.c).
This function calls modper
> On Tue, Apr 22, 2008 at 2:27 PM, Mark Stosberg <[EMAIL PROTECTED]>
> wrote:
> > A. If I just set "status => 404" with CGI.pm / Apache::Registry
> > and return nothing, it works the first time, and then after that I
> >get a lot of these errors:
> >
> >"[Tue Apr 22 13:47:07 2008] [error]
On Wed 23 Apr 2008, David E. Wheeler wrote:
> No subrequest appears at all! So this leads me to conclude one of two
> things. Either
>
> 1. Internally, mod_perl's TransHandler code triggers the subrequest.
> Why it would, I have no idea, but if there is no TransHandler, that
> code doesn't ex
