Since squid caches http it seems more logical to put its cache in
var/cache/squid than var/spool/squid.

Just some thoughts.
		Goswin

Only if squid is capable of gracefully handling the case where files are
arbitrarily removed from squid's cache_dir.  I personally have never tried
this, but I do not think that squid is expected to tolerate it.

If and when it does support such usage, it should use /var/cache/www as
suggested by FHS.

5.5 /var/cache : Application cache data

5.5.1 Purpose

/var/cache is intended for cached data from applications. Such data is
locally generated as a result of time-consuming I/O or calculation. The
application must be able to regenerate or restore the data. Unlike
/var/spool, the cached files can be deleted without data loss. The data must
remain valid between invocations of the application and rebooting the
system.

Files located under /var/cache may be expired in an application specific
manner, by the system administrator, or both. The application must always be
able to recover from manual deletion of these files (generally because of a
disk space shortage). No other requirements are made on the data format of
the cache directories.

Hi,

squid can be made to recover from a loss of its cache by running squid -z.
Its not automatic but I think other stuff in /var/cache also needs some
personal attention after deleting their files.

The FHS specifically says /var/cache/www is for www proxies so that realy should
be used.

MfG
   Goswin

PS: If you still feel squid isn't suited to be in /var/cache/www thats another
bug of squid then. Thats how I see it.

squid will handle removal of files happily, but not directories. We
don't create the directories automatically - patches happily considered.

Rob