httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Graham Leggett <>
Subject Re: svn commit: r951222 - in /httpd/httpd/trunk: CHANGES modules/cache/mod_disk_cache.c
Date Fri, 04 Jun 2010 13:43:34 GMT
On 04 Jun 2010, at 7:27 AM, Ruediger Pluem wrote:

> Why is this needed? mod_cache itself does not allow partial content  
> to be cached
> and even if this does not work it should be fixed there and not in  
> one of the
> storage providers.

mod_cache does allow a 206 to be cached, it is up to the cache  
implementation (mod_disk_cache) to decide whether it wants to handle a  
206 or not.

mod_cache is not the place to fix this. It is entirely valid for a  
cache implementation to be given the opportunity to cache a 206, if  
the cache implementation wants to. It is also entirely valid for a  
cache implementation to choose not to cache a 206 if it doesn't yet  
know how to, and that's what this fix does.

This patch is in response to buggy behaviour discovered in one of the  
UK's news websites, where mod_cache on cluster A was reverse proxying  
content served from origin cluster B. Origin cluster B was reacting to  
range requests with a 206, and cluster A then cached the 206,  
returning it to subsequent visitors. This patch fixes the problem.


View raw message