On Wed, Sep 08, 2004 at 02:19:17PM -0400, Perrin Harkins wrote:
> On Mon, 2004-09-06 at 23:15, Ryan Underwood wrote:
> > I've had this strange problem off and on ever since we started using
> > mod_perl.  Occasionally, when the page is generated and printed, the
> > output goes to the Apache error log instead of to the client
> [...]
> >            PerlHeaderParserHandler "sub { tie *STDOUT, 'Apache' unless tied 
> > *STDOUT; }"
> 
> I suspect either the above hack, or Apache::DynaGzip and
> Apache::RegistryFilter.  These are messing with where your STDOUT gets
> sent and could lead to strange results if something died part-way
> through.

Here's the current config that's been whittled down.  It's still doing
it!  I've no idea what to try next.

---------------------------------------------------

        PerlRequire /path/to/modperl_prepare.pl
        # This was for Apache::StatINC
        PerlSetVar ReloadModules "WixSite::* ABSAdmin::*"

        PerlModule Apache::Registry
        PerlModule Apache::DBI
        PerlWarn on
        PerlTaintCheck on

        <Location /perl>

           SetHandler perl-script
           PerlHandler Apache::Registry

           # Normal stuff
           Options ExecCGI
           allow from all

           # Emulate nph-*.cgi
           PerlSendHeader off

           # Give us %ENV
           PerlSetupEnv on
        </Location>

        <Location /perl-status>
           SetHandler perl-script
           PerlHandler Apache::Status
           PerlSetVar StatusOptionsAll On
           order deny,allow
           deny from all
           allow from .icequake.net
        </Location>

---------------------------------------------------

-- 
Ryan Underwood, <[EMAIL PROTECTED]>

-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html

Reply via email to