You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by Si...@williamslea.com on 2000/08/16 18:47:53 UTC
Errors from Apache.pm
All,
I am seeing the following errors in my apache error log. These have
appeared since moving to a Linux/mod_perl1.24 combination (from NT/1.23)
so I don't know if they come from 1.24 or from the -w switch being handled
better under unix.
Anyone know what these are and how to get rid of them ?
I had a look but I really don't feel confident enough do start playing
around with this module :-)
[Wed Aug 16 17:45:12 2000] null: Use of uninitialized value at
/usr/lib/perl5/site_perl/5.005/i386-linux/Apache.pm line 184.
[Wed Aug 16 17:45:12 2000] null: Use of uninitialized value at
/usr/lib/perl5/site_perl/5.005/i386-linux/Apache.pm line 184.
[Wed Aug 16 17:45:13 2000] null: Use of uninitialized value at
/usr/lib/perl5/site_perl/5.005/i386-linux/Apache.pm line 184.
Many thanks,
Simon Wilcox.
Re: Errors from Apache.pm
Posted by Doug MacEachern <do...@covalent.net>.
On Wed, 16 Aug 2000 Simon_Wilcox@williamslea.com wrote:
>
> All,
>
> I am seeing the following errors in my apache error log. These have
> appeared since moving to a Linux/mod_perl1.24 combination (from NT/1.23)
> so I don't know if they come from 1.24 or from the -w switch being handled
> better under unix.
>
> Anyone know what these are and how to get rid of them ?
>
> I had a look but I really don't feel confident enough do start playing
> around with this module :-)
>
> [Wed Aug 16 17:45:12 2000] null: Use of uninitialized value at
> /usr/lib/perl5/site_perl/5.005/i386-linux/Apache.pm line 184.
> [Wed Aug 16 17:45:12 2000] null: Use of uninitialized value at
> /usr/lib/perl5/site_perl/5.005/i386-linux/Apache.pm line 184.
> [Wed Aug 16 17:45:13 2000] null: Use of uninitialized value at
> /usr/lib/perl5/site_perl/5.005/i386-linux/Apache.pm line 184.
that line is in send_cgi_header(), which means you've configured
PerlSendHeader On. how is your code sending headers? looks like
something that send_cgi_header() can't parse.