Re: [squid-users] acl defined with rep_header used to deny cache is not working

From: Eliezer Croitoru <eliezer_at_ngtech.co.il>
Date: Wed, 13 Nov 2013 13:41:35 +0200

Hey,
On 11/13/2013 01:27 PM, Amos Jeffries wrote:
> Because cache allow/deny control is based on the request in current
> releases of Squid.
Or to change the already considered response cache controls by the
source server.
If the source server thinks it worth caching then the only thing I can
think of is, why not cache? hey should know what is good for him.

> We have a proposal currently going through audit for adding reply based
> allow/deny. That should be available in Squid-3.5 series when that
> process is completed.
There is another option and it is to use ICAP in order to modify the
response Cache related headers ONLY that will reflect that the server
content should not be cached.
But I suggest to choose another method of doing it like:
- properly config the media server
- explicitly deny cache by origin server.

the above is two directions:
1 - the server should be aware of what he is serving and how.
2 - the server content is not welcome in any way to be cached.
(also answers for the below question)

Eliezer

>
>> >Can you suggest any alternative by which I can disable caching for any
>> >response from windows media server?
> Why does it matter?
>
> Amos
Received on Wed Nov 13 2013 - 11:41:52 MST

This archive was generated by hypermail 2.2.0 : Wed Nov 13 2013 - 12:00:03 MST