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).
Thanks,
Sudheer
On Thursday, July 25, 2019, 11:51:07 AM PDT, Jason Yang
<[email protected]> 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.
Best, Juncheng
On Jul 25, 2019, at 14:12, Sudheer Vinukonda <[email protected]> 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
|
|
| |
records.config — Apache Traffic Server 9.0.0 documentation
|
|
|
cache.config — Apache Traffic Server 9.0.0 documentation
|
|
| |
cache.config — Apache Traffic Server 9.0.0 documentation
|
|
|
Does that answer your question?
Thanks,
Sudheer
On Thursday, July 25, 2019, 11:05:34 AM PDT, Jason Yang
<[email protected]> wrote:
Hi there, I am wondering whether ATS supports filtering one-hit-wonders
(do not store them into cache). Thank you!
Best,
Juncheng
