Re: [squid-users] Are "no_cache deny" and "http_access deny" redundant?

From: Brian <hiryuu@dont-contact.us>
Date: Fri, 7 Sep 2001 12:57:00 -0400

They are not the same, but the http_access DOES render the no_cache
useless. 'http_access deny' means it will not service any request
matching that acl (the client gets a permission denied message). no_cache
means it may still service the request, but squid will not save the
response to disk.

So... if you're going to ban requests to that domain entirely, there's not
much point in telling squid to not cache it.

        -- Brian

On Friday 07 September 2001 10:56 am, Steve Snyder wrote:
> Suppose I have this acl defined:
>
> acl blockme dstdomain .blockme.com
>
> and these lines in squid.conf (v2.4S2):
>
> no_cache deny blockme
> http_access deny blockme
>
> Are these last 2 lines redundant? More precisely, does that
> "http_access deny" render the "no_cache deny" useless?
>
> Thanks.
Received on Fri Sep 07 2001 - 10:56:55 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:02:05 MST