[
https://issues.apache.org/jira/browse/TS-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352036#comment-14352036
]
Zhao Yongming commented on TS-965:
----------------------------------
I have no idea of what is the detail, as cache.config is a multi-matching rule
system, and there is some hard-coded rules which is not explained anywhare, for
example: if you matched with 'no-cache', then it will not cache.
I don't like the idea with the cache-control matching, which is hard to extend
and hard to use in real world, maybe we should avoid using it in fever of the
LUA remaping and LUA plugins
> cache.config can't deal with both revalidate= and ttl-in-cache= specified
> -------------------------------------------------------------------------
>
> Key: TS-965
> URL: https://issues.apache.org/jira/browse/TS-965
> Project: Traffic Server
> Issue Type: Bug
> Components: Cache
> Affects Versions: 3.1.0, 3.0.1
> Reporter: Igor Galić
> Assignee: Alan M. Carroll
> Labels: A, cache-control
> Fix For: 5.3.0
>
>
> If both of these options are specified (with the same time?), nothing is
> cached at all.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
