mod_perl2, CGI.pm and sending own headers

I am having an extrememly frustrating experience getting my old mod_perl1 scripts from a RedHat 7.3 server working on a new CentOS4 box with Apache 2.0.52 server with mod_perl 2.0.1 with CGI.pm 3.11 I have a mod_perl script area set tup with SetHandler perl-script PerlRe

Re: mod_perl2, CGI.pm and sending own headers

Paul Raines wrote: > > I am having an extrememly frustrating experience getting my old > mod_perl1 scripts from a RedHat 7.3 server working on a new CentOS4 box > with Apache 2.0.52 server with mod_perl 2.0.1 with CGI.pm 3.11 I'm sorry to hear that. I would expect the migration of Registry scrip

Re: mod_perl2, CGI.pm and sending own headers

On Mon, 28 Aug 2006, Geoffrey Young wrote: Paul Raines wrote: I am having an extrememly frustrating experience getting my old mod_perl1 scripts from a RedHat 7.3 server working on a new CentOS4 box with Apache 2.0.52 server with mod_perl 2.0.1 with CGI.pm 3.11 I'm sorry to hear that. I woul

Best Practices Question

What is a better route to go?   Have a handler in Apache call a package directly using a handler() – having the module itself parse out arguments passed in and loading configuration files based on argument values. Build a script in /cgi-bin/ that uses mod_perl2, par