Yea cache promote should do you what you want, set the buckets value and hits appropriately sized for the amount of requests you get on that remap (or plugin wide) and the amount of times you wish to have seen it before allowing it in to cache

On Thu, Jul 25, 2019 at 1:15 PM Sudheer Vinukonda <> wrote:
Nice to know, TIL! Thank you!

On Thursday, July 25, 2019, 12:12:30 PM PDT, Jason Yang <> wrote:

Great to know! Thank you! 


On Jul 25, 2019, 15:05 -0400, Jeremy Payne <>, wrote:
What about the 'cache promote' plugin ?

On Thu, Jul 25, 2019 at 2:01 PM Sudheer Vinukonda <> wrote:
Ah, very interesting. That requires an additional mechanism to maintain the state (first or subsequent access) across requests. Yeah, AFAIK, this will need a new plugin (don't believe there's anything built-in or pre-existing to support this).



On Thursday, July 25, 2019, 11:51:07 AM PDT, Jason Yang <> wrote:

Hi Sudheer, 
    Thank you for your quick reply! It seems the option you proposed is a general control. Writing a plugin is indeed one option, but to avoid reinventing the wheel, I just want to double check that ATS does not have this function. To be specific, I don’t want to cache an object when I first time see it. In other words, I only want to cache objects that have been seen at least twice. 


On Jul 25, 2019, at 14:12, Sudheer Vinukonda <> wrote:

Hmm..not entirely sure if I understand the question, but, if you are asking ATS supports skipping cache on some requests, yes. There's different ways of doing that. You can disable cache per remap line using records.config — Apache Traffic Server 9.0.0 documentation or use cache.config or write a plugin for more finer control

On Thursday, July 25, 2019, 11:05:34 AM PDT, Jason Yang <> wrote:

Hi there, 
    I am wondering whether ATS supports filtering one-hit-wonders (do not store them into cache). Thank you!