On Thursday 11 May 2006 02:00 am, Lionel MARTIN wrote:
> Hi,
> I'v really tried to reduce everything to a minimum to insulate the problem.
> So, here's the config file:
> #####
> ServerName MYSERVER
> ServerRoot "C:\Program Files\Apache
> Group\Apache2\TestingFromScratch\ApacheModPerl"

On the offchance, try taking the space out of the filename.

> DocumentRoot "htdocs"
> Listen 80
> LoadModule mime_module ../../modules/mod_mime.so
> LoadModule log_config_module ../../modules/mod_log_config.so
> # for mod_perl
> LoadFile "c:/TempApache/Perl/bin/perl58.dll"
> LoadModule perl_module ../../modules/mod_perl.so
> SetHandler perl-script
> PerlResponseHandler ModPerl::Registry
> PerlOptions +ParseHeaders

What happens if you change that to ModPerl::PerlRun?

> TransferLog logs/access.log
> ErrorLog logs/error.log
> TypesConfig conf/mime.types
> LogLevel debug
> #####

you get an appropriate entry in the access log?

> and here's the script (/perl/warning.pl):
> #####
> warn "Hello You Script\n";
> use strict;
> print "Content-Type: text/html\n\n";
> print "I think I issued a warning";
> #####

Does it make any difference if you move the warn to the end (it shouldn't)?

Does anything different happen if you access the page more than once? If you
shut down the server afterwards?

What happens if you run in single process mode?

I don't know the windows side of things, so I don't know if that makes any
difference. I'm not seeing anything wrong with your config. On unix I'd look
for permissions problems. Does apache run as a seperate user or with changed
permissions after startup?

"But life has to be more than just a pulse-beat.
What we hold sacred gives our lives meaning."
Sinclair in Babylon 5: Believers