Re: no_cache/always_direct

Brian wrote:
>
> Sorry to keep asking questions on this, I just want to make sure I
> understand correctly.
>
> Assume the following access list:
>
> acl local1 dst 208.206.76.0/24
> no_cache deny local1
>
> Now correct me if I am wrong, but what this means is that objects
> from web sites on the 208.206.76.0/24 networks will not get cached.
>
> Or should it read acl local1 src 208.206.76.0/24? The bottom line, is
> that I don't want objects on the 208.206.76.0/24 network to be cached, if
> a web page is hosted on that network, don't cache the page.

dst refers to where the page is fetched from (the web-server).
src refers to who is requesting the page (the client)

> Ok, and another acl example:
>
> acl local1 dst 208.206.76.0/24
> always_direct allow local1
>
>
> My understanding of the above is that if the destination of an http
> request is in 208.206.76.0/24, then always go DIRECT.
>
> so, something like:
>
> acl local1 dst 208.206.76.0/24
> no_cache deny local1
> always_direct allow local1
>
> Would totally make sure that any content from 208.206.76.0/24 was not
> cached and that the client went directly to the source.

acl's cannot be used to control whether the client makes a request for
an object through your proxy or not. That's only configurable in the
client.

D
Received on Fri Jul 23 1999 - 20:10:21 MDT