You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by Matt Sergeant <ma...@sergeant.org> on 2000/07/03 16:47:45 UTC

User pressed stop?

Every so often I get:

Broken pipe: client stopped connection before rflush completed

In my error log. Is that the "user pressed stop" condition? AxKit just
sends raw files (unless in no_cache mode), i.e. it sets $r->filename() and
then returns DECLINED. Do I need to handle this, or can I just ignore it?

-- 
<Matt/>

Fastnet Software Ltd. High Performance Web Specialists
Providing mod_perl, XML, Sybase and Oracle solutions
Email for training and consultancy availability.
http://sergeant.org | AxKit: http://axkit.org


Re: User pressed stop?

Posted by Eric Cholet <ch...@logilune.com>.
> Every so often I get:
> 
> Broken pipe: client stopped connection before rflush completed
> 
> In my error log. Is that the "user pressed stop" condition? AxKit just
> sends raw files (unless in no_cache mode), i.e. it sets $r->filename() and
> then returns DECLINED. Do I need to handle this, or can I just ignore it?

ap_rflush is called to write data to the client, but the write fails.
It's a normal "user pressed stop" condition, ap_rflush issues the
info message and sets c->aborted so that subsequent writes will not
reach the network. You can ignore the message, it is printed because you
have LogLevel >= info. 

--
Eric