Hi

Thanks for all your help.  If I print out the header line myself, before
anything else is printed out, then for some reason none of the images
are produced.  Images are produced dynamically using perl and GD.  If I
leave everything alone, I get images that work properly but no HTTP
header;  If I hack away and print the HTTP header myself, then the
header looks fine but my images don't get produced (it's not that the
URLs are wrong, the img-tmp/ directory remains empty).

I don't pretend to understand this, nor do I expect you to, needless to
say it's not as easy as just printing the headers myself.

Finally, thanks for the tip RE 'PerlOptions +ParseHeader'; it made
little difference, but at least now that part of the code is correct.

Thanks again

Mick

-----Original Message-----
From: Clinton Gormley [mailto:[EMAIL PROTECTED] 
Sent: 16 April 2007 11:32
To: michael watson (IAH-C)
Cc: Clinton Gormley; modperl
Subject: RE: Malformed header from script

On Mon, 2007-04-16 at 11:12 +0100, michael watson (IAH-C) wrote:
> That does indeed make the HTML headers come through, however, I get
> about 20 "Content-type: text/html" lines in my web page because that
> print function is used to print out ALL HTML, not just the headers.

Then just print the header before you do any other printing.

> 
> httpd.conf has:
> 
> $Location{"/perl"}={
>   SetHandler      =>  'perl-script',
>   PerlHandler     =>  'ModPerl::Registry',
> #  Options         =>  '+ExecCGI',
>   allow           =>  'from all',
>   PerlSendHeader  =>  'On',
> };

Also, PerlSendHeader is a mod_perl 1 config option, which has been
replaced by 'PerlOptions ParseHeader'

Take a look here for the docs on configuring mod_perl 2
http://perl.apache.org/docs/2.0/user/config/config.html

Clint


Reply via email to