Hi Eric My understanding is that Squid honours the expires as per the origin server. Of course, you can fiddle with the caching rules and times to your hearts content, but once you do, you are approaching no-man's land, because you're departing from the protocols ... Surely the best approach will be to set the correct expiry thresholds on the origin, and leave the caches to deal with these as per HTTP-imposed conditions? That way you alleviate those concerns, because once _you_ start fiddling, what's to stop anyone else fiddling also ...? But I guess I'm being naïve. ;-) Cheers and good luck with that! J. > -----Original Message----- > From: Eric Blanchi [mailto:ebb@xxxxxxxxxxxxxx] > Sent: Thursday, 24 November 2005 4:13 PM > To: squid-users@xxxxxxxxxxxxxxx > Subject: Reverse Proxy: Age > > Hi, > I'm thinking of using Squid as a reverse proxy and I've got a question: > > - If one uses min_age and max_age (and overrides expiry and last_mod) to > keep an object for a long time in cache. Would other caches around the > internet -such as ISP caches for example- be mislead by it and store the > object for a long time without re-checking it? > > Here is more details: I would like to keep the objects in cache for a > very long time and only manually purge and reload them. To do so I would > set the min_age and max_age in the refresh_pattern to be very high. I > would not be happy though if because of that age, other caches > (transparent ISP caches) would keep those object for a long time and > never let clients access my reverse proxy. > > I have the impression that the age is only dealt with internally to > Squid as in clients requesting pages would not care of the age of an > object by itself. And clients on the outside would not even be aware > that they are talking to a proxy (as it is in reverse mode). > > Is this correct? > > I hope this makes sense. > Any help very much appreciated. > > Cheers. > -- > Eric B. Blanchi
