[squid-users] Need better debug_options values to track down cache MISSes

[Greg]

> From: Pavel Kazlenka <pavel.kazlenka at measurement-factory.com>
> To: squid-users at lists.squid-cache.org
> Subject: Re: [squid-users] Need better debug_options values to track
>         down cache MISSes
> Message-ID: <54EC9147.6070301 at measurement-factory.com>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
> Hi Greg,
>
> I use this combo to check if request is cached or no and why:
> debug_options 20,9 27,9 31,9 70,9 82,9 22,9 84,9 90,9
>
> Then in cache.log file you can search by 'YES' or 'NO' (uppercase) to
> see if the content is cacheable (and cached) or not and the reason of
> this decision. Hope this will help.

Thanks, that was useful! I've tried that; the results:
- First access (at least from my computer in this session):
http://pastebin.com/EHNJ9N6F
- Second access (plus HTTP headers): http://pastebin.com/u8ZsHQfk

It's rather strange. Even though it's "cacheableReply: YES", it seems
that the system stores the page with key
C284A5F1C95D3B6C6D0F37A54517BEC9 but searches for it with
F588DBC3D17E4F32409C1AF22FC627FE in both test cases. (But in all
fairness, these might be different keys, I don't know the code too
well.)

Could you take a look at the debug log?

Best regards,
Greg