Re: Debugging inappropriately cached objects

On Mon, 3 Apr 2000, Bert Driehuis wrote:

> I've looked through the docs and the code, and didn't find an answer to
> this one... Is there any tool that I can feed a URL, and it'll tell me the
> logic Squid uses to cache the thing?
>
> I'm thinking of something like the cachemgr output like:
>
> KEY 2FE024C9792767C97F6992548D1BA5F6
> GET http://www.cramsession.brainbuzz.com/images/spacers/gutter.gif
> STORE_OK IN_MEMORY SWAPOUT_DONE PING_DONE
> CACHABLE,DISPATCHED,VALIDATED
> LV:954671839 LU:954671875 LM:954472056 EX:-1
> 0 locks, 0 clients, 1 refs
> Swap File 0X022D29
> inmem_lo: 0
> inmem_hi: 293
> swapout: 417 bytes done, 293 queued, FD -1
>
> ... but cachemgr needs to have a way to enter the URL.
>
> Am I overlooking something, or should I just add it? Or, the usual
> suspect, has it been implemented since 2.2?

I'm not sure how this would work. You want squid to tell you why
it cached something? The closest thing that I can think of is
Mark Nottingham's cachability checker:
    http://www.mnot.net/cacheability/

Squid works by basically reponses as cachable by default, and then
looking for reasons NOT to cache them.

Duane W.
Received on Sun Apr 02 2000 - 22:16:53 MDT