> From: Justin Erenkrantz [mailto:[EMAIL PROTECTED]] > > On Sun, May 05, 2002 at 08:03:24PM +0200, Graham Leggett wrote: > > I understand the Content Length filter is responsible for sorting out > > Content-Length, and that chunked encoding will be enabled should the > > length be uncalculate-able, so it works as it is - but the question is, > > if we already have a content-length, should we not just keep it? > > Nah, this allows us flexibility in optimizing the data sent to our > client. If we can send chunked-encoding, I believe that is a better > than using C-L. I believe that the RFC allows us to do these sorts > of optimizations. > > IIRC, the PR wasn't saying there was a problem with our approach - it > was just that the admin didn't understand that was legal. -- Justin
To the best of my knowledge, Doug actually fixed this problem after the 2.0.35 release. We should keep the C-L unless we are modifying the content. To throw away the C-L means that we are removing information that can be used to help determine if the content has changed. Ryan
