Stas Bekman wrote:
If the connection is aborted filters need to know how to deal with that situation and not waste resources processing data which is going to be dumped anyway. It's easy to do by checking c->aborted every so often. The question is, what's the proper response code should the filter return if it decides not to process data any longer since it saw c->aborted is true? AP_NOBODY_WROTE?
AP_FILTER_ERROR?
What's confusing is that it seems that most consumers (not filters) (e.g. in protocol.c) that call ap_pass_brigade are completely ignoring its response code.
I suppose cleanly aborting the request is at least important for the logging purposes.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
