Re: [squid-users] RELEASE/304 messages in store.log

From: Adrian Chadd <adrian@dont-contact.us>
Date: Wed, 5 Mar 2008 12:52:03 +0900

Check to see if the object is actually in cache. I bet that the
RELEASE line you're seeing is the temporary store entry that was
created purely to return the 304 message.

Adrian

On Tue, Mar 04, 2008, Chris Woodfield wrote:
> Hi,
>
> We recently added the "reload-into-ims" directive to our squid config
> after noticing that a large number of queries were coming in with No-
> Cache set, killing our cache efficiency. We have a relatively short
> max-age set, working on the assumption that the If-Modified-Since will
> keep the unchanging content from being continually refreshed.
>
> Looking in our store.log, however, we're seeing lots of this:
>
> 1204650204.462 RELEASE -1 FFFFFFFF 2435DD617A6A5750936E71A36D77AF8F
> 304 1204635071 1204057533 -1 image/jpeg -1/0 GET
> http://example.com/object.jpg
>
> I'm unsure if the meaning of this. The "RELEASE" line suggests that
> the object in question was deleted from the cache store, but the 304
> suggests that a 304 Not-Modified was sent to the client.
>
> Any insights? I can't imagine that the object should be purged from
> cache if a Not-Modified is returned, but I can't tell if it actually
> is or not...
>
> -C

-- 
- Xenion - http://www.xenion.com.au/ - VPS Hosting - Commercial Squid Support -
- $25/pm entry-level VPSes w/ capped bandwidth charges available in WA -
Received on Tue Mar 04 2008 - 20:37:45 MST

This archive was generated by hypermail pre-2.1.9 : Tue Apr 01 2008 - 13:00:04 MDT