[SQU] PATCH: identifying uncacheable objects

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Content-Type: text/plain; charset=us-ascii

Hi folks - I've been trying to get some clues as to which objects
passing through our caches aren't actually cacheable, and why. Here's
a patch for Squid which other folk doing this sort of thing might find
useful ...

  http://martinh.net/squid-hacks/2.2STABLE5/nocache-reason.diff
  http://martinh.net/squid-hacks/2.3STABLE4/nocache-reason.diff
  http://martinh.net/squid-hacks/2.4DEVEL4/nocache-reason.diff

(sorry, not got one against the current CVS codebase)

Here's what it does...

If ident lookups are disabled at build time by giving configure the

  --disable-ident-lookups

argument, the ident field in the Squid access log is replaced by a
tag which indicates (for uncacheable objects) why the object was
considered uncacheable. Cacheable objects are represented with a
'-' character.

This patch may be useful for people trying to build up a picture of
the volume of uncacheable traffic seen by their servers, and those
sites which are most responsible for it.

Cheers,

Martin

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999 + martin

iD8DBQE6FR4cVw+hz3xBJfQRAgWnAKCrU4cyTb2pj9bjTnNYjZ00d5DWHgCfeQXE
zUnzWU+FRRODEKS0br/dQFU=
=Rfns
-----END PGP SIGNATURE-----

--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html