One approach that comes to mind is to print smaller chunks of the response and between those check $r->connection->aborted to see if the connection is still alive. However I don't think you'll be successful with that approach since the connection is broken while printing to the client.
Are you trying to surpress the error message or fix the problem? The problem seems to be that your javascript is causing the connection to time out. Maybe increase the keep alive timeout? On Wed, Aug 4, 2010 at 7:34 PM, <seasproc...@gmail.com> wrote: > Error logs are filling up with strange "File does not exist" errors and code > is trapping Apache exception: > Apache2::RequestIO::print: (53) Software caused connection abort > These errors are repeatably caused by client breaking the connection before > page has loaded (page loads slowly because of extensive javascript). > Is Apache misconfigured? Is my code failing to handle interrupt? Guidance > greatly appreciated! > Server: Apache/2.2.15 (FreeBSD) mod_ssl/2.2.15 OpenSSL/0.9.8e DAV/2 > mod_perl/2.0.4 Perl/v5.10.1 > Framework: Catalyst > > -- > Bikewise: http://www.bikewise.org > > > >
