On 03 Sep 2010, at 12:53 AM, Nick Kew wrote:
I disagree about 'broken': a cache isn't *required* to cache ranges.
I definitely agree that a cache isn't required to cache ranges, but
right now mod_cache actively forbids the caching of ranges by an
implementation, and that's the behaviour that's currently broken.
As for third-party backends, this change is at serious risk of
breaking
anything that has (perfectly reasonably) ignored range responses.
Fine for trunk, but not for a stable branch.
Good point, in that case I withdraw the backport, this makes sense.
Regards,
Graham
--
