Re: [squid-users] Forcing refresh for certain source IPs

Hello Henrik,

can you think of another way to accomplish what I want?

Regards,
Hans

Henrik Nordstrom <hno@squid-cache.org> on Nov 10, 2001:
>
> no_cache only stops content from being cached, not cache hits. This is
> how no_cache is designed. If you want it to function in another manner
> then code changes is required.
>
>
> Hans Juergen von Lengerke wrote:
> >
> > I am trying to set up acl's for an accelerator squid that would force
> > squid to refresh objects when developers access the accelerated website.
> > I got it working when _only_ developers access the website but as soon
> > as someone else accesses an object, developers will get a cached
> > response of the object rather than a fresh one. Here is my access
> > control configuration:
> >
> > ## Access controls
> > ##
> > acl manager proto cache_object
> > acl localhost src 127.0.0.1/255.255.255.255
> > acl example src 194.120.114.6/255.255.255.255
> > acl developer src 194.120.114.3/255.255.255.255
> > acl all src 0.0.0.0/0.0.0.0
> > acl SSL_ports port 443 563
> > acl Safe_ports port 80 21 443 563 70 210 1025-65535
> > acl Safe_ports port 280 # http-mgmt
> > acl Safe_ports port 488 # gss-http
> > acl Safe_ports port 591 # filemaker
> > acl Safe_ports port 777 # multiling http
> > acl CONNECT method CONNECT
> > no_cache deny developer
> > http_access allow all
> > miss_access allow all
Received on Mon Nov 12 2001 - 01:53:49 MST