Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: domain of pwood@christianbook.com
 designates 4.17.160.157 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Modify output of Apache::PerlRun?
Date: Mon, 10 Mar 2008 10:28:32 -0400
Message-ID: <E0F0BBC78185F94D8608A18CFC37FA23060AE80F@raptor.cbdadmin.com>
In-Reply-To: <66887a3d0803071225n379053d1j25f622636c407256@mail.gmail.com>
Thread-Topic: Modify output of Apache::PerlRun?
Thread-Index: AciAnc1ImgEqfZNASqKOkU4D5VCEaQCHI+lw
From: "Peter Wood" <pwood@christianbook.com>
To: "Perrin Harkins" <perrin@elem.com>
Cc: <modperl@perl.apache.org>

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: pharkins@gmail.com [mailto:pharkins@gmail.com] On=20
> 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?
>=20
>=20
> On Fri, Mar 7, 2008 at 1:27 PM, Peter Wood=20
> <pwood@christianbook.com> wrote:
> > So, I've given Apache::Filter and Apache::PerlRunFilter=20
> (from CPAN) a =20
> > shot, and the actual filtering action seems to work as expected,=20
> > except  that just before my own filter is applied, the=20
> first line of=20
> > input goes  missing.
>=20
> I don't know what's going on, but I can confirm that this=20
> didn't happen to me when I used this module years ago.  Have=20
> you tried playing with PerlSendHeader?
>=20
> - Perrin
>=20