no_cache/always_direct

From: Brian <signal@dont-contact.us>
Date: Fri, 23 Jul 1999 14:33:30 -0500 (CDT)

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.

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.

I am just not sure in my first acl example (for no_cache) of that should
be src or dst.

Brian

-----------------------------------------------------
Brian Feeny (BF304) signal@shreve.net
318-222-2638 x 109 http://www.shreve.net/~signal
Network Administrator ShreveNet Inc. (ASN 11881)
Received on Fri Jul 23 1999 - 13:17:19 MDT

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