* Stas Bekman <[EMAIL PROTECTED]> wrote:
in 2.0 - Connection output filters don't recieve the EOS bucket when the request method is HEAD. This breaks the idiom of flushing any stored data
when the eos bucket is seen. And some filters could be broken because of
that.
I believe that is because of broken handlers, which don't send anything if they detect HEAD. In 2.0 a handler should not care about GET or HEAD, but send all the time its data, so that all the processing (C-L filter etc) works properly.
I see that with a non-broken handler which sends the response body unconditionally. The output I've posted in my original email is all that's seen by an output connection filter.
Besides, shouldn't the output connection filter see the response data nevertheless? otherwise how can you calculate a correct C-L when the filter weren't given a change to change the data, potentially changing its length.
I'm talking about dynamic handlers, not static data here.
__________________________________________________________________ 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
