On Wed, Feb 11, 2004 at 10:37:30AM -0800, Stas Bekman wrote:
> Stefan Traby wrote:
> >Hi !
> >
> >I do not say that this is a bug, ok?
> >It's just not compatible with old mod_perl :)
>
> mod_perl 1.0 doesn't use perlio layers.
Cool, and where is the point? :)
> >If STDOUT is crippled mod_perl-1.99_12 dies,
> >while 1.2x does not:
>
> But you don't explain what you mean by a crippled STDOUT.
>
> Take a look at this test:
> t/api/internal_redirect.t # client side
> t/response/TestAPI/internal_redirect.pm # server side
>
> can you change it to reproduce your problem?
easily:
--- internal_redirect.pm.orig 2004-02-11 19:43:40.000000000 +0100
+++ internal_redirect.pm 2004-02-11 19:43:54.000000000 +0100
@@ -21,6 +21,7 @@
else {
# main-req
my $redirect_uri = $args{uri};
+ close STDOUT;
$r->internal_redirect("$redirect_uri?main=modperl");
}
As I pointed out in my previous mail,
modperl_io_perlio_override_stdout
expects that STDOUT on input is valid which makes it incompatible
with mod_perl_1.2x.
And yes, I think that this is a bug (just because the function has "override"
in it's name). You can override an invalid handle.
So the error is to croak when "dup" fails.
BTW: I have other issues which I don't know if they are mod_perl or apache
specific.
One bug is that stopping apache (using apachectrl stop) causes the whole
perl engine to startup, which is stupid.
The config-parser is completely broken on correct configuration:
asp:~# httpd -t -DSSL
Syntax OK
asp:~# httpd -t
Syntax error on line 1230 of /usr/websys/conf/httpd.conf:
Expected </Perl>> but saw </Perl>
asp:~#
(clearly line 1230 contains: "<IfDefine SSL>")
--
ciao -
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
