Howdy, Thanks for the PerlSendHeader tip! It was set to 'On' for the host I was working with, and after changing it to 'Off', things started working. We're using CGI.pm to print out HTTP headers for all of our CGI scripts, so PerlSendHeader shouldn't be necessary. I'm assuming that there must have been some conflict between the parsing/reformatting PerlSendHeader did, and that done by Apache::PerlRunFilter - perhaps PerlSendHeader was sending one less newline than PerlRunFilter was expecting, and it therefore chomped an extra line? It would be nice to understand exactly why this fixed the problem, but for now I'm happy just with the fix.
Also, just for future reference, the maintainer of Apache::Filter, Ken Williams, has indicated to me that he is no longer able to support any of his Apache::* modules, and recommends going to the mod_perl mailing list for support. Glad I did! Thanks again, Peter > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Perrin Harkins > Sent: Friday, March 07, 2008 3:26 PM > To: Peter Wood > Cc: modperl@perl.apache.org > Subject: Re: Modify output of Apache::PerlRun? > > > On Fri, Mar 7, 2008 at 1:27 PM, Peter Wood > <[EMAIL PROTECTED]> wrote: > > So, I've given Apache::Filter and Apache::PerlRunFilter > (from CPAN) a > > shot, and the actual filtering action seems to work as expected, > > except that just before my own filter is applied, the > first line of > > input goes missing. > > I don't know what's going on, but I can confirm that this > didn't happen to me when I used this module years ago. Have > you tried playing with PerlSendHeader? > > - Perrin >
