thanks miles, i actually found in the cache 2 variants (different Accept-Encoding:)
Miles Libbey wrote > On Tue, Dec 12, 2017 at 2:46 AM, ezko < > erez.koler@ > > wrote: >> thanks for the suggestion miles. >> >> i checked the cache as you suggested. I think its OK. There are no >> unexpected query strings , or other noticeable object variations. >> proxy.process.cache.wrap_count seems low , and I don't see any non-GET >> verbs. >> >> I suspect there is something wrong with the way Cache-control max-age >> header >> is set. >> If for example I set Cache-control max-age to 4 seconds , when ATS >> caches >> the object , how does it decide when the object is expired ? I assumed it >> will simply expire the object after 4 seconds. Is that true ? , or are >> there >> any other affecting factors ? > > The main other factor I can think of is around Vary:. ATS will store > (up to 5 by default) variants. So, when the request comes in, ATS > picks the variant that best matches the request. If the object varies > on user-agent (of which there are zillions), there is likely not going > to be a match. > >> looking into the diag.log - can I spot ATS making a COLD decision ? > > I'm not sure. We use cacheStatus=% > <chm> > in our logs > https://docs.trafficserver.apache.org/en/7.1.x/admin-guide/logging/formatting.en.html > >> thanks in advance. >> >> >> >> >> >> -- >> Sent from: http://apache-traffic-server.24303.n7.nabble.com/ -- Sent from: http://apache-traffic-server.24303.n7.nabble.com/
