Frank Wiles wrote:
.------[ Ask Bjoern Hansen wrote (2002/09/19 at 01:47:39) ]------This has been changed to do the right thing around mid-Sep I believe. Previously httpd was buffering up the output and calculating the Content-Length header before sending the HTTP headers. It doesn't do that anymore, which is a relief for us. I've discovered this just before my presentation, where I've planned to demonstrate that bad behavior using the filter snooper, but there was no need any more :)
| | On Wed, 18 Sep 2002, Josh Chamas wrote:
| | [...]
| > So I run it again with ServerTokens Min, and get the same results. :)
| > Still something different on the mod_perl headers, looks like mod_perl
| > 2.x is setting Content-Length where it didn't use to.
| | The details evade me, but I recall something about how the buckets
| work in the httpd that makes httpd 2.0 always know (and set) the
| Content-Length.
| | There was discussion about changing it; but I don't remember the
| outcome.
You can still inject a cl filter which will buffer the data and calculate its length e.g. to be cache friendly, if that's your intention.
Actually, returning to Issac's question regarding releasing the handler early, you need a slightly modified version of the cl filter to do that. Since it's already buffering the data, you just want to do this unconditionaly.
__________________________________________________________________
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
