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
scripts to be fairly painless, almost transparent. handlers, sure, they
would take some migration time. but at any rate, I'm sorry you're
frustrated.
>
> I have a mod_perl script area set tup with
>
> <Directory /home/httpd/facility>
> SetHandler perl-script
> PerlResponseHandler ModPerl::Registry
> PerlOptions -ParseHeaders
I think if you take this out and also get rid of the -nph option here
> my $head = header(-type=>$mimetype,-nph=>1,
^^^^^^^^^
you'll be ok. the script
use CGI qw/:standard :html3/;
print header(-type => 'application/pdf',
-Content_length => 392,
-expires => 'now');
produces the following HTTP response
HTTP/1.1 200 OK
Date: Mon, 28 Aug 2006 16:49:18 GMT
Server: Apache/2.2.2 (Unix) mod_perl/2.0.3-dev Perl/v5.8.8
Expires: Mon, 28 Aug 2006 16:49:18 GMT
Content-length: 392
Connection: close
Content-Type: application/pdf
followed by my data. the config is simply
<Location /registry>
SetHandler perl-script
Options +ExecCGI
PerlResponseHandler ModPerl::Registry
PerlOptions +ParseHeaders
</Location>
which is the config from the ModPerl::Registry test suite. in fact, I
just dunked a test script in the proper directory and fired up the test
suite and a telnet session to test it.
I hope this resolves your problem. in the future, please see
http://perl.apache.org/bugs/
and follow the steps there so that you provide us the details about your
installation, such as CGI.pm version, etc.
HTH
--Geoff
