On Mon, 5 Mar 2001, Chris DeCenzo wrote:
> 
> Hi.
> 
> I notice that when I have a false cache hit among my sibling caches, the 
> page ultimately fetched from the origin web server is not cached.
> 
> In other words:
> - client sends request to first cache.
> - first cache deduces from cache digest that page sits on second cache.
> - first cache places request to second cache.
> - second cache returns MISS.
> - first cache places request to origin web server.
> - first cache returns response from origin web server to client.
> - first cache does not cache this response.
> 
> Regarding the last step, why would the first cache not cache this response? 
> Is this by design?
> 
> I am using Squid 2.3 stable 3 build with cache digests enabled. My Squid 
> caches are all siblings to one another (ie. no parents), and I would prefer 
> not to turn on miss_access among my sibling caches.
It shouldn't be happening that way.  Are you sure its not an isolated 
case?  Maybe the page is uncachable for some other reason?
-- To unsubscribe, see http://www.squid-cache.org/mailing-lists.htmlReceived on Mon Mar 05 2001 - 14:33:30 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:58:32 MST