How is the cause of a False Hit determined?
Assume A requests a URL from B and receives a False Hit • Using the squidclient utility PURGE the URL from A, e.g. squidclient -m PURGE ‘URL’ • Using the squidclient utility request the object from A, e.g. squidclient ‘URL’ The HTTP headers of the request are available. Two header types are of particular interest: • X-Cache – this shows whether an object is available or not. • X-Cache-Lookup – this keeps the result of a store table lookup before refresh causing rules are checked (i.e. it indicates if the object is available before any validation would be attempted). The X-Cache and X-Cache-Lookup headers from A should both show MISS. If A requests the object from B (which it will if the digest lookup indicates B has it – assuming B is closest peer of course 🙂 then there will be another set of these headers from B. If the X-Cache header from B shows a MISS a False Hit has occurred. This means that A thought B had an object but B tells A it does not have it available for retrieval. The
