OK... life is better after re-visiting: <http://perl.apache.org/docs/2.0/user/coding/coding.html#Generating_HTTP_Response_Headers>
and just using: use Apache2::RequestRec (); $r=Apache2::RequestUtil->request; $r->content_type($mime_type); in the few places where these scripts print their own headers. I've yet to rewrite/replace the other areas where they print headers (i.e. Cookies, Redirects, etc.) and plan to use something like: use Apache2::Const -compile => qw(REDIRECT); $r->headers_out->set(Location => $location); return Apache2::Const::REDIRECT; but for now, it appears that we're on the right track. Hope this thread can help others. On Tuesday 12 July 2005 13:22, Bill Whillers wrote: > The test machine is running: > > CGI 3.10 > Apache/2.0.54 (Unix) > mod_perl/2.0.1 > Perl/v5.8.5 > > On Tuesday 12 July 2005 13:12, Bill Whillers wrote: > > Thanks Geoff, > > > > I'm not suggesting this is a 'bug' at this point however I'd like to find > > (or solicit) more info about this. > > > > The is some kind of buffering issue. I've isolated that this only happens > > serving pages exceeding a specific size (7716 bytes) (??). > > > > httpd.conf uses: > > > > <Location /test/> > > SetHandler perl-script > > PerlResponseHandler ModPerl::Registry > > PerlOptions +ParseHeaders > > Options +ExecCGI > > </Location> > > > > > > Thanks > > > > On Tuesday 12 July 2005 11:59, Geoffrey Young wrote: > > > Bill Whillers wrote: > > > > Can someone on the list share any information about this? > > > > > > please file a proper bug report: > > > > > > http://perl.apache.org/bugs/ > > > > > > specifically, running t/REPORT will let us know which versions of > > > CGI.pm and mod_perl you're using so we don't need to guess. > > > > > > --Geoff