[
https://issues.apache.org/jira/browse/TS-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680751#comment-14680751
]
Alan M. Carroll commented on TS-3426:
-------------------------------------
What is desired is a single point where the plugin can set one of three values:
1) Default - do the default thing as if the plugin had done nothing.
2) Do not cache - do not cache the transaction.
3) Do cache - cache the transaction if possible.
There are few complications. The primary one is checking to see if the
transaction is cacheable via {{TSHttpTxnIsCacheable}} which should ignore this
value. That is, it should return a value as if the setting was "default"
otherwise you get in to circularity problems.
It should also be noted that "is possible" covers the cache being entirely
disabled. In that case nothing will be cached regardless of setting this
override.
This would replace (at a minimum)
* {{TSHttpTxnServerRespNoStore}}
* {{proxy.config.http.cache.http}} as overridable (this configuration would
become restart only)
* {{TSHttpTxnUntransformedRespCache}}
* {{TSHttpTxnTransformedRespCache}}
> Consolidate the multiple API for disabling cache
> ------------------------------------------------
>
> Key: TS-3426
> URL: https://issues.apache.org/jira/browse/TS-3426
> Project: Traffic Server
> Issue Type: Improvement
> Components: TS API
> Reporter: Sudheer Vinukonda
> Assignee: Alan M. Carroll
> Labels: A
> Fix For: 6.1.0
>
>
> There are currently multiple API (see below) that can be used by a plugin to
> disable cache for a given transaction.
> {{TSHttpTxnServerRespNoStoreSet}}, {{TSHttpTxnReqCacheableSet}},
> {{TSHttpTxnRespCacheableSet}}
> Opening this jira to analyze whether these are redundant and consolidate if
> necessary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
