Client Cache

A client cache hit occurs when a client performs an up-to-date check on a document and the remote server returns a 304 message telling the client that the document was not modified. An up-to-date check initiated by a client indicates that the client has its own copy of the document in the cache.

For the client’s cache, the report shows:

• Client and proxy cache hits: A client cache hit in which the proxy server and the client both have a copy of the requested document and the remote server is queried for an up-to-date check with respect to the proxy’s copy and the client’s request is then evaluated with respect to the proxy’s copy. The cache performance report shows the number of requests of this type that the proxy serviced and the average amount of time it took to service these requests.

• Proxy shortcut no-check: A client cache hit in which the proxy server and the client both have a copy of the requested document and the proxy server tells the client without checking with the remote server that the document in the client’s cache is up-to-date. The cache performance report shows the number of requests of this type that the proxy serviced and the average time used to service these requests.

• Client cache hits only: A client cache hit in which only the client has a cached copy of the requested document. In this type of request, the proxy server directly tunnels the client’s If-modified-since GET header. The cache performance report shows the number of requests of this type that the proxy serviced and the average time used to service these requests.

• Total client cache hits: the total number of client cache hits and the average amount of time used to service these requests.