no_cache still caching?

From: Edwin de Graaf <>
Date: Wed, 9 Sep 1998 11:33:45 +0200 (MET DST)

Hello Squid users,

Because some of our clients don't really trust Squid to not return stale
objects, they want to have the option of disabling all caching. Because
they are behind a firewall they still have to go through Squid. I want
to run two Squid processes on the firewall, one that does caching, and
one that doesn't.

I am using Squid 1.1.22, and I have configured the no_cache directive like
        acl nocache proto HTTP
        no_cache deny nocache

After doing this I have stopped the Squid process, emptied the cache with
squid -z and restarted Squid. In the access log file I find the following:

905338421.773 1403 TCP_MISS/200 3941 GET
 - DIRECT/ text/html
905338423.378 738 TCP_MISS/200 2647 GET
images/apache_pb.gif - DIRECT/ image/gif
905338423.807 1382 TCP_MISS/200 5649 GET
images/apachecon.gif - DIRECT/ image/gif
905338429.780 7409 TCP_MISS/200 23762 GET
/images/apache_logo.gif - DIRECT/ image/gif
905338446.766 18 TCP_HIT/200 3941 GET
- NONE/- text/html

Unless I misunderstand the log file the last line shows that Squid is still
caching, even with the no_cache directive.

Before use the proto HTTP acl I have also tried using src
as acl for the no_cache directive. Also I am quite sure that I am using
the right Squid proxy (the one that should not cache), this one is logging
to a different logfile and running on a different port.

I would appreciate any suggestions you may have.

Best regards,
Edwin de Graaf
Received on Wed Sep 09 1998 - 02:38:16 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:41:54 MST