Actually, it looks like using APR::Error [1] and wrapping $f->print in an eval would do the trick...?
Jeff [1] http://perl.apache.org/docs/2.0/api/APR/Error.html On 5/1/05, Jeff Ambrosino <[EMAIL PROTECTED]> wrote: > [Sun May 01 05:12:21 2005] [error] [client X.X.X.X] > Apache::Filter::print: (104)Connection reset by peer at > /var/httpd/lib/perl/MyOutputFilter.pm line > 453n\tMyOutputFilter::handler('Apache::Filter=SCALAR(0x87106a8)', > 'APR::Brigade=SCALAR(0x86eac6c)') called at -e line 0\n\teval {...} > called at -e line 0\nApache::Filter: (103) Software caused connection > abort at -e line 0 .... > I assume the errors are due to the end user clicking "stop" or > navigating away from the page before it has finished being sent... > but is there a [more elegant] way of trapping these events from within > my mod_perl filter?
